Re: improving docs (was: Break_Align_Order-3)

On Fri, 14 Mar 2003 23:48:21 -0700 Paul Scott [EMAIL PROTECTED] wrote: I can certainly do some of that. My next concern/question would be concerning versions. I use whatever is packaged for Debian unstable - currently 1.6.6. Is there much point improving that documentation when the

\mark fixed

In the following Lilycode there are two instances of \mark. They are generating errors: *** error: syntax error, unexepected DIGIT: \mark 1 (\mark 2) *** Are you sure the digit wasn't in quotes the times it worked? I know that: \mark 1 works for me and is shown that way in the

1.7 fixes

...If the \mark had a two digit number the lack of quotes didn't cause any problems. Putting in the quotes fixed it. This is a bug which I fixed in 1.7 CVS. So in 1.7 are the quotes necessary? I'd like to move up to 1.7.x for the ability to put text markup over block rests. How stable is it?

1.7 fixes

[EMAIL PROTECTED] writes: ...If the \mark had a two digit number the lack of quotes didn't cause any problems. Putting in the quotes fixed it. This is a bug which I fixed in 1.7 CVS. So in 1.7 are the quotes necessary? I'd like to move up to 1.7.x for the ability to put text markup

Re: 1.7 fixes

David == David Bobroff [EMAIL PROTECTED] writes: David I'd like to move up to 1.7.x for the ability to put text David markup over block rests. How stable is it? My experience with the 1.5-1.6 transition is that 1.5 was stable over most of it's life in the sense of not producing

Re: 1.7 fixes

Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: ...If the \mark had a two digit number the lack of quotes didn't cause any problems. Putting in the quotes fixed it. This is a bug which I fixed in 1.7 CVS. So in 1.7 are the quotes necessary? I'd like to move up to

Re: multiple \scores in a lily-book included file?

Any reason for needing separate 'score' starts. It seems you want to use the 'sequential' capability, something like \score { \transpose c'{ \scale } \transpose g' { \scale } \transpose d'{ \scale } } This would run the c' scale, followed immediately by then the g', etc. Or, by

Re: 1.7 fixes

I've used 1.7.13 since release (+ about 1 week), 1.7.12 for about 1 month before 13 - absolutely no crashes, no unexpected output, etc. I am very pleased. My environment is Linux - SuSE 8.0, and I rebuilt the latest version of all the prerequisite programs (needed Bison 1.875a to complete the

Re: multiple \scores in a lily-book included file?

On Sat, 15 Mar 2003 10:49:28 -0700 Hans Forbrich [EMAIL PROTECTED] wrote: Any reason for needing separate 'score' starts. It seems you want to use the'sequential' capability, something like The scale example was the simplest to explain, but I agree that it doesn't really need seperate score

Clef change before first note

I need an organ right-hand staff in which the first symbols are G clef, key signature, time signature, F clef, eight rest, notes, etc The G clef is not visible. How can I force the G clef to show up, then display the F clef as a (smaller) clef-change symbol? -- Daniel Ashton PGP key

Re: Clef change before first note

On Sat, 15 Mar 2003 18:21:13 -0500 Daniel Ashton [EMAIL PROTECTED] wrote: I need an organ right-hand staff in which the first symbols are G clef, key signature, time signature, F clef, eight rest, notes, etc The G clef is not visible. How can I force the G clef to show up, then

Brackets

Hello, How can I put accidentals in between brackets? And is there a better way to achieve this on articulation (and how to center it): g4^#'(columns ((font-relative-size . 1) ([ )) ((raise . 0.8) (music scripts-mordent)) ((font-relative-size . 1) (])) ) -- Best regards,

Slurs going both directions

Is this possible? The music I'm typesetting has a voice going from the right-hand staff to the left-hand staff. (I'm using the \translator function.) Four quarter-notes are slurred together, the first two on the upper staff with stems down, the second two on the lower staff with stems up.

Re: multiple \scores in a lily-book included file?

I agree to a certain extent. Judicious use of music and { music } and \break - along with a very strict naming rules (drawing on years of large project s/w coding experience) - helped me recently (70+ page Cantata). You are however quite correct - the source score blocks are very, very ugly.

Re: Slurs going both directions

Look at the examples, tips trickx andregression tests - I seem to remember exactly that situation in one of them. Specifically check http://lilypond.org/development/input/test/out-www/test.html (or http://lilypond.org/stable/input/test/out-www/test.html) and search for slur ... /Hans