bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1988 in lilypond: Patch: Rename \markuplines to \markuplist (b


From: lilypond
Subject: Re: Issue 1988 in lilypond: Patch: Rename \markuplines to \markuplist (before running convert-ly)
Date: Mon, 24 Oct 2011 05:20:30 +0000


Comment #2 on issue 1988 by address@hidden: Patch: Rename \markuplines to \markuplist (before running convert-ly)
http://code.google.com/p/lilypond/issues/detail?id=1988

A markup list exactly is _not_ lines. It is the state that has _not_ yet been turned into lines. When you use them as markup, they get turned into a block of lines, but the whole point of their existence is that you want the state before that, just like a music list becomes sequential music only when used as music. But there still is, say, \simultaneous { c e g } where the music list is used differently.

Or
`\concat' ARGS (markup list)
     Concatenate ARGS in a horizontal line, without spaces in between.
     Strings and simple markups are concatenated on the input level,
     allowing ligatures.  For example, `\concat { "f" \simple #"i" }' is
     equivalent to `"fi"'.

It does not make sense that you have to write
zap=\markuplines { a b c }
\markup \concat \zap

to get a tight line of abc.

And markup lists are documented explicitly as markup lists. Just the command for calling them is different. Totally confusing.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]