bug-lilypond
[Top][All Lists]

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

 From: Paul Morris Subject: Re: page-break-permission = ##f doesn't work for the final manual \pageBreak Date: Mon, 24 Feb 2014 16:57:12 -0500

```On Feb 24, 2014, at 3:38 PM, Federico Bruni <address@hidden> wrote:

> No, my fault: you should change the value of ragged-last-bottom:
>
> \paper {
>   ragged-last-bottom = ##f
> }

Ah, ok, thanks.  Glad to know there's already a way to achieve this.

> If the point of setting page-break-permission = ##f is to "insert page
> breaks at explicit \pageBreak commands and nowhere else" as the docs say...
> and yet there is an easily reproducible case where breaks are always
> inserted where there is no explicit \pageBreak, despite the presence of an
> explicit \pageBreak where the break should go, and would go if there were
> more music after it...  I'd call that a bug.
>
> I assume that fixing this would entail improving \pageBreak so it works even
> when there is no object following it? (i.e. when it is the last command in
> the input)
>
>
> You should ask a comment from a developer, but I don't think that this
> request makes sense. Also because of ragged-last-bottom, which already fixes
> this case.

Hmmm...  one way to look at this is that the docs here:
http://lilypond.org/doc/v2.18/Documentation/notation/explicit-breaks

give the impression that LilyPond has a mode that will _only_ insert breaks
where there are explicit break commands (***and nowhere else***).  But is that
actually the case?  The following leads you to think there is such a "manual
break only" mode:

"When line-break-permission is overridden to false, Lily will insert line
breaks at explicit \break commands ***and nowhere else***. When
page-break-permission is overridden to false, Lily will insert page breaks at
explicit \pageBreak commands ***and nowhere else***."

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."

Thanks for your help and for considering this.  I've started another thread