James E. Bailey wrote: > I don't know where in the documentation this is...
It's in Trevor's patch from 9 hours ago: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blobdiff;f=Documentation/user/input.itely;h=2bf35cf51d0bc7c938bf148ae271f9acc341b075;hp=b20cc4ebf33679d5fe13165e64dc2c9c3e8a7a7f;hb=0d1d63151f21a3b3af3ec01aad3908562fba11e0;hpb=d511b69c1cb8836bc0b7b49b9f396cf06fef19ac > ...but Lyrics Explained (2.1.2) explains why this particular > (i.e., LyricText) example is necessary. > Incidentally, just trying it shows that it's necessary... I see my mistake... it's only in \lyricmode. Trevor's patch is actually clearly worded; I'm just not used to reading texinfo. If I had carefully observed the hierarchy of @item commands, I would have understood. +...@item Around every opening and closing curly bracket. +...@item After every command or variable, i.e. every item that +begins with a @code{\} sign. +...@item After every item that is to be interpreted as a Scheme +expression, i.e. every item that begins with a @code{#} sign. +...@item To separate all elements of a Scheme expression. +...@item In @code{lyricmode} to separate all the terms in both +...@code{\override} and @code{\set} commands. In particular, spaces +must be used around the dot and the equals sign in commands like +...@code{\override Score . LyricText #'font-size = #5} and before and +after the entire command. Sorry for the noise. - Mark _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
