> Le 14 avr. 2023 à 09:13, Valentin Petzel a écrit :
>
> A markup list is a list of markups,
This ain’t true, since \markuplist \table … is a markup list but not a Scheme
list of markups, unlike \markuplist { a b c }, but I agree with the rest of
your post.
Best,
Jean
> how should \column not be the "right" way? A markup list is a list
> of markups, but does not contain any information about how these
> should be positioned. [...]
In hindsight everything's clear now, thanks :-)
Werner
Hello Werner,
how should \column not be the "right" way? A markup list is a list of markups,
but does not contain any information about how these should be positioned. The
default behaviour Lilypond does when encountering a toplevel markuplist or
when having a markuplist in a score is to stack
> What do you mean by “convert”?
Probably bad wording: I mean to wrap a markup list into a markup.
> I don’t know what it means to convert a markup list to a markup,
> since there are many ways in which you can combine the stencils:
> \column, \center-column, \line, \concat, \fill-line, etc.
I
> Le 12 avr. 2023 à 11:07, Werner LEMBERG a écrit :
>
> What's the proper way to convert a `\markuplist` to a `\markup`?
> `lilypond-book` splits a top-level `\table` into separate lines; I
> want to avoid that because it prevents fine-tuning of the vertical
> spacing of rows. Right now I d
What's the proper way to convert a `\markuplist` to a `\markup`?
`lilypond-book` splits a top-level `\table` into separate lines; I
want to avoid that because it prevents fine-tuning of the vertical
spacing of rows. Right now I do
```
\markup \column {
\table ...
}
```
Werner
