On Oct 24, 2011, at 8:57 AM, David Kastrup wrote:
> "m...@apollinemike.com" <m...@apollinemike.com> writes:
>
>> \markup { \column { \italic foo bar }} would use line as its layout
>> manager and have two elements, one markup that used nothing as its
>> layout manager (markups with 1 element cannot have layout managers)
>> and had no transformations and one markup that used nothing as its
>> layout manger and had an italic transformation.
>>
>> In this representation, box-layout-across-pages could be a layout
>> manager that works like markuplines. The page breaker would take all
>> top level markups, check the layout managers, and automatically create
>> chunks based on the layout manager being used.
>
> Will
>
> z = \markuplist { a b c }
> \markup { \concat \z }
>
> still work? That is one of the reasons I want "\markuplist" rather than
> "\markuplines" since it has nothing to do whatsoever with lines before
> it actually gets put into a context wanting to interpret it as such.
>
Ah, I see what you mean.
Yes, this makes sense. A list of markups would get passed to a layout manager
that would deal with it.
Cheers,
MS
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
