Graham Percival <[EMAIL PROTECTED]> writes: >> Between that section and the following one, the functions used to >> access >> and set music properties may be introduced. > > Err, ok. I added all this pretty much as you explained it here, but > I'm not sure that I understood it fully. Could you check this section > when we have another release to make sure I didn't omit or change > anything important?
Ok, I'll look at it then >> 11.3.3 Adding articulation to notes (example) >> >> I don't know where you got this example from, but there are mistakes. > > From you, :) > http://lists.gnu.org/archive/html/lilypond-devel/2006-05/msg00039.html yes I remembered, that was self-derision :-) >> The wording is poor: cons does not modify the existing list. Maybe that >> should be precised, for instance: (without modifying the original >> list). > > Hmm... how's this? > [EMAIL PROTECTED]' is used to add an element to a list without modifying the > original list. ok >> 11.4.1 Markup construction in Scheme >> >> "One can not feed the #:line, #:center, or #:column) commands with a >> variable or the result of a function call." >> >> This sentence should more general, we're talking here about commands >> accepting markup-list arguments, eg. #:line, #:center-align or #:column >> (but there are others, like #:fill-line). > > Does this work? > Commands which accept markup-list arguments (such as > @code{#:line}, @code{#:center}, [EMAIL PROTECTED]:column}) cannottake > commands with a variable or commands which are the > result of a function call. hm. I don't understand some instances of the word command in some places. The markup-list argument of commands such as @code{#:line}, @code{#:center}, or @code{#:column}, cannot be a variable or the result of a function call. nicolas _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
