bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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 05:18:30 -0800 (PST)

Federico Bruni-5 wrote
> I'm not sure if it's really a bug. On 2.16.2 the same happens.
> I guess that pageBreaks needs an object afterwards, otherwise it doesn't
> make sense. You can use an empty \markup to work around the problem:

That's a helpful workaround (thanks!), although you end up with an extra
blank page that you don't really want. So I'd say the need for such a
workaround indicates an area for improvement (if not a bug).  

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)

If this is a "won't fix" then I'd suggest that that part of the docs should
be edited to be more accurate, maybe to indicate this is a "known issue" or
something like that.


Speaking of the docs for this, the example given here:
http://lilypond.org/doc/v2.18/Documentation/notation/explicit-breaks

is not so good since the output is actually the same when you comment out
the commands that it is intended to illustrate:

% \override NonMusicalPaperColumn.line-break-permission = ##f
% \override NonMusicalPaperColumn.page-break-permission = ##f

(It is a good demonstration of ragged-bottom and ragged-right, however.)  To
improve it the number of measures on some of the lines and the number of
lines per page would need to be increased so that they are large enough to
trigger an automatic line break or page break if these commands were not
present.  

Thanks for considering,
-Paul



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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]