Re: [Fwd: Re: numbers as arguments in define-markup-command]

2006-12-30 Thread Graham Percival
Han-Wen Nienhuys wrote: I suggest to replace this: "Every piece of LilyPond input needs to have {curly braces} placed around the input. For the rest of this manual, most examples will omit these braces, but don't forget them in your own music!" with this (also note the inserted whitespace arou

Re: [Fwd: Re: numbers as arguments in define-markup-command]

2006-12-30 Thread Orm Finnendahl
Am 29. Dezember 2006, 21:57 Uhr (+0100) schrieb Han-Wen Nienhuys: > > no, the rule is that you have to end a #...scheme... expression with space I see. It still might be useful to mention in the docs. I'm not sure how many users easily distinguish between #...scheme... expressions and music expre

Re: [Fwd: Re: numbers as arguments in define-markup-command]

2006-12-29 Thread Han-Wen Nienhuys
Han-Wen Nienhuys escreveu: >> #10 } > > o.k., thanks! I take from this example that in general it's safer to > delimit all brackets with whitespace characters on both sides to avoid > ambiguities. no, the rule is that you have to end a #...scheme... expression with space -- Han-Wen Nienhuys

[Fwd: Re: numbers as arguments in define-markup-command]

2006-12-29 Thread Han-Wen Nienhuys
-- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com --- Begin Message --- Am 29. Dezember 2006, 20:26 Uhr (+0100) schrieb Han-Wen Nienhuys: > try > > #10 } o.k., thanks! I take from t