Am Do., 29. Nov. 2018 um 09:33 Uhr schrieb Richard Shann
<rich...@rshann.plus.com>:
>
> On Wed, 2018-11-28 at 15:45 +0100, Lukas-Fabian Moser wrote:
> > > Sorry, I should have made it clearer that this index is being
> > > automatically generated. Now you point out that there is an
> > > \autoOageBreaksOff, which is what I thought I needed, I realize
> > > that it
> > > wouldn't help - I would need to turn them off and back on between
> > > each
> > > entry in the hope that LilyPond would take advantage of such an
> > > Off/On
> > > sequence to insert a page break in between if needed, which I'm
> > > sure it
> > > wouldn't :(
> >
> > I'm not sure I understand you correctly, but it is perfectly possible
> > to
> > forbid page breaks between arbitrary markup lines:
> yes, that's what I needed to do, and I'm now doing that - it's working
> fine now. What I didn't realize was that Lily will not put page breaks
> inside a \markup {} - Harm pointed this out to me via his \column
> {\line .. \line ...} example, Lily does not break at any of the
> \lines.
> Once he'd tipped me off I looked again at the docs and saw that,
> although they don't quite explicitly say that Lily will not page break
> inside a markup block it is implied by the bit of the docs I quoted
> "The \pageBreak and \noPageBreak commands may also be inserted [...]
> between [...] top-level markups."
> Perhaps the Docs should contain an explicit statement there that no
> automatic breaking will happen inside a \markup {} ...
>
> RichardWell, in NR 1.8.1 Writing text one can read about toplevel markup/markuplist: " Separate text ... Separate text blocks can be spread over multiple pages, making it possible to print text documents or books entirely within LilyPond. This feature, and the specific syntax it requires, are described in Multi-page markup. ... " And later " Multi-page markup Although standard markup objects are not breakable, a specific syntax makes it possible to enter lines of text that can spread over multiple pages: " Could you suggest how to improve this? Cheers, Harm _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
