Re: Stanza Numbers for 2.1.11 on Cygwin

Rob V [EMAIL PROTECTED] writes: Can't find property type-check for 'stz' ,[ ChangeLog ] | 2003-12-31 Han-Wen Nienhuys [EMAIL PROTECTED] | | * scm/define-translator-properties.scm: remove | melismaEngraverBusy, stz property. ` -- Thanks, Jeff

Loading lilypond-mode fails on emacs startup

() ` -- Thanks, Jeff , | Jeffery B. Rancier | | Softechnics | a METTLER TOLEDO company ` ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

Re: Lyrics too far from notes

Mats Bengtsson [EMAIL PROTECTED] writes: The property setting means that the lyrics is typeset within a rectangle that extends at least 3 units down (that's that -3) and 3 units up elative to the baseline of the lyrics. This rectangle is then put next to the rectangle where the stave is

Re: constructive criticism

Dave Pawson [EMAIL PROTECTED] writes: If the documentation were in docbook, its far more approachable than texinfo (IMHO). Any thoughts on what Norm Walsh says here: http://norman.walsh.name/2003/05/21/docbook -- Thanks, Jeff ___ Lilypond-user

Re: 2.1.6 Cygwin packages available at my homepage

Fodor Bertalan [EMAIL PROTECTED] writes: I've built a 2.1.6 package. Now it seems to be full and OK. Hello Fodor, When cygwin starts downloading, it reports lilypond 2.01-1. Is that correct? -- Thanks, Jeff ___ Lilypond-user mailing list [EMAIL

cygwin mirrors

Hi All, Does anyone know where I can download the latest cygwin version of lilypond? Is there a particular mirror which gets the updates first? I'm currently using: , | bash-2.05b$ lilypond --version | lilypond (GNU LilyPond) 2.0.1 ` -- Thanks, Jeff

Re: Strange behaviour

Han-Wen Nienhuys [EMAIL PROTECTED] writes: Nothing, really. For some reason (\addlyrics is quite broken, I prefer not to know), a short lived LyricsVoice context is created that spans the rest. The ending of the LyricsVoice is before the first note, does not have any spacing parameters to

notes lyrics won't line up

Hi All, This is my first real attempt, although it took a some time, Emacs helped quite bit. I've got a couple quick questions: How can I assign names to the voices showing up to the left of the first line? E.g., Soprano | Alto|

Staffgroup question

Hi All. I've been fiddling with the satb.ly template, trying to create a barbershop quartet template. My question: Why can I get away with specifying the time signature once in the first staff, and have it default to the same in the lower staff, but not have the key signature behave the same

Re: Trouble starting Lilypond

Mats Bengtsson [EMAIL PROTECTED] writes: LilyPond is probably fairly different from most other programs you have experienced before and it's definitely one where you have to read at least the tutorial before you can do anything useful at all. Agreed. Is learning Scheme a subtle requirement?

2.0.1 (Cygwin) fails after running convert-ly

Pardon me if this list is not for this type of error. I just ran lilypond on source was working pre-2.0.1. I ran convert-ly with the '-f=1.7.18' option in my source, as that was the version indicated. Here is the non-verbose output: , | lilypond (GNU LilyPond) 2.0.1 | Running usr... | Now

Re: [Lilypond-User] 2.0.1 (Cygwin) fails after running convert-ly

namespace conflict? I'll rename them and try again. -- Thanks, Jeff , | Jeffery B. Rancier | | Softechnics | a METTLER TOLEDO company ` ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

Re: 2.0.1 (Cygwin) fails after running convert-ly

, nevertheless, and got the same errors. But in answer to your question, I did convert them as well. -- Thanks, Jeff , | Jeffery B. Rancier | | Softechnics | a METTLER TOLEDO company ` ___ Lilypond-user mailing list [EMAIL PROTECTED] http

Re: 2.0.1 (Cygwin) fails after running convert-ly

: old relative compatibility was not used. ` -- Thanks, Jeff , | Jeffery B. Rancier | | Softechnics | a METTLER TOLEDO company ` ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

cygwin install problem

1 jrancier Domain U 3459584 Sep 30 12:25 lilypond-bin.exe | -rwxr-xr-x1 jrancier Domain U41712 Sep 30 12:14 lilypond-book ` , | bash-2.05b$ which ly2dvi | ly2dvi: Command not found. | bash-2.05b$ ` Any ideas? -- Thanks, Jeff , | Jeffery B. Rancier | | Softechnics

Re: spacer lyric?

Mats Bengtsson [EMAIL PROTECTED] writes: See http://mail.gnu.org/archive/html/lilypond-user/2003-02/msg00217.html for some different solutions to the problem. I wasn't aware of the archive. I start there. Cheers, Mats. -- Thanks, Jeff , | Jeffery B. Rancier | | Softechnics | a METTLER

Re: documentation

Aaron [EMAIL PROTECTED] writes: I have friends who I am trying to win over to lilypond, but they keep telling me its to complicated. an example to illustrate: -( -) slur would be much clearer for a newbie if it had notes attached to it. c4-( d4 e4-) and it doesn't take up much more

spacer lyric?

Is there such a way I can create a 'spacer lyric'? E.g. if I have a four part song, which shares the same lyrics 90% of the time, but differs the remaining 10%, I don't want to print duplicate lyrics 4 times, 90% of the time. I want to space the lyrics out until they diverge. I read the manual

StaffGroup question

Why in the following example does 'lower' staff inherit the time signature property, but not the key signature? And is this the right place to set them? (This is from the satb.ly template?) And is 's1' just a name holder to associate each Lyrics and Staff contexts with each other? , |

automaticMelismata question (bug?)

, Jeff , | Jeffery B. Rancier | | Softechnics | a METTLER TOLEDO company ` ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

Re: automaticMelismata question (bug?)

Ignore this. I saw the bug mentioned in the documentation. Sorry. [EMAIL PROTECTED] (Jeffery B. Rancier) writes: In my StaffGroup context (from input/template/satb.ly), the following is set: \property Score.automaticMelismata = ##t Can I assume that should extend my lyric to the next