Jay Anderson <[email protected]> writes:

> On Wed, Aug 5, 2015 at 10:48 AM, David Kastrup <[email protected]> wrote:
>> Jay Anderson <[email protected]> writes:
>>> #(add-score #{ \noPageBreak #})
>>
>> Which version should that ever have worked in?
>
> I haven't figured out when it changed (git bisect), but it at least
> worked in 2.19.15. (With the added parser attribute "#(add-score
> parser #{ \noPageBreak #})")

No, it didn't.  In version 2.19.21, the default compilation options
changed to have assertion failures triggered by default.  It's more or
less pure luck that you did not get a crash for that code.

Something _valid_ (with current function call conventions) would be

#(add-score #{ \score { \noPageBreak } #})

but \noPageBreak does not seem meaningful as the sole content of a
score.  Is there a reason you cannot just use

\noPageBreak

on its own?

-- 
David Kastrup

_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to