bug-lilypond
[Top][All Lists]
Advanced

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

Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do


From: Phil Holmes
Subject: Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not)
Date: Mon, 21 Jun 2010 15:29:26 +0100

"Dmytro O. Redchuk" <address@hidden> wrote in message news:address@hidden
У вт, 2010-03-23 у 08:25 -0600, Carl Sorensen пише:
The clue here is that there is some kind of break in the middle of the score
that you've put in manually that confuses the layout engine.
My fault!

Just remove the /pageBreak in the middle of your score and it works
perfectly.
Yes, almost .)

(I can use both system-count and page-count, replace \pageBreak with
\break, then adjust spacing to force three-systems-per-page desired
layout, with ragged-bottom=##t --- of course! Now i can see. Thank You.)

I've found issue 884, but here is something different --- here lilypond
can not produce anything, because of confusing \pageBreak. Well, if i
could provide tiny example, i would add issue titled "\pageBreak
confuses layout engine *far* too much"... But i can not, i guess.
I will try .)

Oh well.

Thank You anyway!
Thank You for Your time, sorry. My fault, in some sense, surely. Again.

HTH,

Carl

--
 Dmytro O. Redchuk

So I'm going to break Graham's Bug Squad rule again here, and ask a question. As far as I can see, this shows a critical bug. It may be complex as a bit of Lilypond, but surely something that compiles and displays perfectly under 2.12 should do the same under 2.13? This bit of code runs fine with the \pageBreak in 2.12 and crashes with no output and lots of programming errors in 2.13.24-2.

--
Phil Holmes
Bug Squad





reply via email to

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