Re: is Score.LyricText really a bad syntax?

[Mark Polesky]

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.

address@hidden Around every opening and closing curly bracket.
address@hidden After every command or variable, i.e. every item that
+begins with a @code{\} sign.
address@hidden After every item that is to be interpreted as a Scheme
+expression, i.e. every item that begins with a @code{#} sign.
address@hidden To separate all elements of a Scheme expression.
address@hidden In @code{lyricmode} to separate all the terms in both
address@hidden and @code{\set} commands.  In particular, spaces
+must be used around the dot and the equals sign in commands like
address@hidden Score . LyricText #'font-size = #5} and before and
+after the entire command.

Sorry for the noise.
- Mark