I seem to have found the error - the slur went from
one context to another. Fixed now!
- J. Garcia
P.S. Please forgive my newbie-ness
__
Do you Yahoo!?
Yahoo! Domains Claim yours for only $14.70/year
http://smallbusiness.promotions.yaho
Huge of O E M software. Try to find cheaper ;)
Windows, Office, Photoshop etc.
http://teddychoice.biz/index.php?s=5706
mbf znxtttx rpki oyxewlou tdjqv
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Hi everybody !
Bonjour tout le monde !
Very glad to reach this mailing list : I've beginning with Lilypond2.0 since 3 months,
and
discovered some tricks on my own, but I still very depend on what you know about it !
So, a few
questions :
1. I'd like to edit some of my music in lanscape layout :
Hi!
I get
warning: cannot find Voice: choir
when compiling the attached file. The output nevertheless
seems good. The warning disappears if I comment out the
\set command. Where should I put it to avoid warnings?
\version "2.2.1"
\score {
<<
\new Staff {
\set Staff.midi
In case anybody is interested I have managed to solve the problem I posed a few days
ago with reference to the "repeat-shorter-bracket.ly" example. This produces exactly
what I wanted. A cut down version is:
% Generated by lilypond-book
% Options: [printfilename,texidoc,linewidth]
\paper {
Hi again ! I've just forgotten a question : does a french traduction group exist for
Lilypond ? If
not, who would be interrested in it ? I've already contacted traduc.org, but I've
receive no answer
yet...
Au revoir pour de bon !
___
lilypond-user m
Hi,
I don't understand why the following snippet does not give the desired
result.
I get two clefs one after the other...
%%
\version "2.2.1"
\score {
\notes <<
\new Staff {
\clef bass
\time 2/4
r2
}
On Tuesday 18 May 2004 20.44, Steve Shorter wrote:
> Howdy!
>
> I have a smallish .ly file that will crash lilypond 2.2.1 on Debian Woody.
> Is this a bug or is there somthing wrong with the source file. It parses
> without any other errors or warinings.
This bug will be fixed in 2.2.2, but