Re: is Score.LyricText really a bad syntax?

2009-06-22 Thread 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=b20cc4ebf33679d5fe13165e64dc2c9c3e8a7a7

Re: is Score.LyricText really a bad syntax?

2009-06-22 Thread James E. Bailey
On 22.06.2009, at 19:17, Mark Polesky wrote: 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. Really? What's the risk of doing Score.LyricText? Non-spaced context

is Score.LyricText really a bad syntax?

2009-06-22 Thread Mark Polesky
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. Really? What's the risk of doing Score.LyricText? Non-spaced context.grob dots are all over the docs; do we need to c