[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LilyPond strings and \markup
From: |
Neil Puttock |
Subject: |
Re: LilyPond strings and \markup |
Date: |
Mon, 17 Aug 2009 22:18:56 +0100 |
2009/8/17 Graham Percival <address@hidden>:
> Alternately, we could be stricter about this -- I wouldn't mind if
> we insisted that people use
> \override foo #'bar = #5
> instead of allowing the non-# form, if then we could state as a
> general rule that overrides required a # after the =
That's fine for simple overrides with numbers and strings, but would
be very confusing for novice users trying to wrestle with the correct
syntax for markup in scheme (when they're probably already struggling
with \markup { } syntax).
Regards,
Neil
- LilyPond strings and \markup, Mark Polesky, 2009/08/16
- Re: LilyPond strings and \markup, Patrick McCarty, 2009/08/16
- Re: LilyPond strings and \markup, Joe Neeman, 2009/08/16
- Re: LilyPond strings and \markup, Carl Sorensen, 2009/08/17
- Re: LilyPond strings and \markup, Mark Polesky, 2009/08/17
- Re: LilyPond strings and \markup, Trevor Daniels, 2009/08/17
- Re: LilyPond strings and \markup, Joe Neeman, 2009/08/17
- Re: LilyPond strings and \markup, Graham Percival, 2009/08/17
- Re: LilyPond strings and \markup,
Neil Puttock <=
- Re: LilyPond strings and \markup, Graham Percival, 2009/08/17
- Re: LilyPond strings and \markup, John Mandereau, 2009/08/18
- Re: LilyPond strings and \markup, Nicolas Sceaux, 2009/08/18