Carl Sorensen wrote" <c_soren...@byu.edu> Friday, September 04, 2009
3:06 PM
Also, as you plan sections, remember that anything using \set or
\override
belongs in a snippet, not in the main text body.
This certainly is a rule for NR 1, but is not
absolutely essential for NR 2. But in general
you're right - self-contained snippets are usually
the best way of demonstrating \set and \override
commands. When appropriately tagged and referenced
they appear in the manual exactly as they would if
placed there, and can be easily modified by anyone.
I would add: don't discuss the actual command in
the text - use an example - as examples will be
automatically updated with convert-ly; text will not.
In order to have a
meaningful manual, this may require the addition of some new
LilyPond
commands, which is *not* a problem.
And is to be recommended if it results in an
easier user interface.
Trevor
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
