Re: page-break-permission = ##f doesn't work for the final manual \pageBreak

[Eluze]

Paul Morris wrote
> But what it says at the top of that page is a little different:
> 
> "Lily sometimes rejects explicit \break and \pageBreak commands. There are
> two commands to override this behavior:"
> 
> If that is the more accurate account of what these commands do, then they
> don't really prevent automatic breaks from being inserted.  They just
> prevent explicit breaks from being ignored/rejected.  If that's the case
> then I think the next part should be revised like this:
> 
> "When line-break-permission is overridden to false, Lily will _always_
> insert line breaks at explicit \break commands. When page-break-permission
> is overridden to false, Lily will _always_ insert page breaks at explicit
> \pageBreak commands."

I think there are 2 contexts where page breaks occur or don't:

in this example LilyPond does not allow a page break and compresses the
first page like wild (but warns).

the following 3 \score's should be placed on 1 page but LilyPond silently
goes to a new page when the page is full.

\layout{
  \context{
    \Score
    \override NonMusicalPaperColumn.page-break-permission = ##f
  }
}
\score{{\repeat unfold 105 {c'1 \break }}}
\pageBreak
\score{{ \repeat unfold 7 {c'1 \break }}}
\score{{ \repeat unfold 7 {c'1 \break }}}
\score{{ \repeat unfold 7 {c'1 \break }}}

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/page-break-permission-f-doesn-t-work-for-the-final-manual-pageBreak-tp159763p159924.html
Sent from the Bugs mailing list archive at Nabble.com.