Updates:
Status: Verified
Comment #26 on issue 884 by PhilEHolmes: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
(No comment was entered for this change.)
___
bug-lilypond mailing list
Comment #22 on issue 884 by n.puttock: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
I've checked this with the versions of Lily that I have, and the
behaviour is incorrect from 13.31 onwards.
The original snippet correctly produces two pages on
Comment #23 on issue 884 by percival.music.ca: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
ok, let's move Colin's example into a new issue number, then mark this one
as fixed again (and add back the tag for the version number in which it was
On Wed, 2010-12-29 at 00:33 +, lilyp...@googlecode.com wrote:
Comment #23 on issue 884 by percival.music.ca: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
ok, let's move Colin's example into a new issue number, then mark this one
as
Updates:
Status: Fixed
Comment #24 on issue 884 by ColinPKCampbell: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
Created issue 1465 \pageBreak breaks \page-ref
___
bug-lilypond mailing list
Updates:
Labels: fixed_2_13_25
Comment #25 on issue 884 by pnorcks: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
(No comment was entered for this change.)
___
bug-lilypond mailing list
Comment #20 on issue 884 by PhilEHolmes: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
I've checked this with the versions of Lily that I have, and the behaviour
is incorrect from 13.31 onwards.
Updates:
Owner: ---
Labels: -Priority-High Priority-Critical
Comment #21 on issue 884 by percival.music.ca: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
Why downgrade the priority? if it was Critical before, it's Critical now.
Updates:
Status: Verified
Comment #18 on issue 884 by brownian.box: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
(No comment was entered for this change.)
___
bug-lilypond mailing list
Comment #16 on issue 884 by perpeduumimmobile: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
The list version has one major benefit: it's considerably faster.
Which seems to back up my conjecture that deducing the optimal chunk sizes
seems hard
Comment #17 on issue 884 by joeneeman: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
No, we don't iterate over all possible configurations. We use a dynamic
programming algorithm whose running time is quadratic in the length of the
book. In the
Updates:
Status: Fixed
Comment #12 on issue 884 by joeneeman: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
To be picky, \pageTurn doesn't work like this because the page-turn-breaker
doesn't listen to page-count. But anyway, I've reverted
Comment #13 on issue 884 by perpeduumimmobile: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
That should be more intuitive. Does it mean min-systems-per-page is now
obsolete?
Either way, is it possible to keep the list definitions of
Comment #14 on issue 884 by joeneeman: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
No, min-systems-per-page still works, but it won't be as good at finding
solutions if the constraints are very strange (the regression tests still
work,
Comment #15 on issue 884 by perpeduumimmobile: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
Okay, thanks.
If the list version is not an absolutely low-hanging fruit, as I assumed
after your second-to-last commit, I'd too leave it as a (very)
Updates:
Status: Fixed
Labels: fixed_2_13_25
Comment #2 on issue 884 by joeneeman: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
I have changed the workings of page-count so that it interacts better with
\pageBreak. Now, page-count
Comment #3 on issue 884 by kie...@alumni.rice.edu: pageBreak resets
page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
Hi Joe,
It seems intuitive to me that page-count be absolute, and that \pageBreak
simply indicates where the page *must* break within those
Comment #4 on issue 884 by kie...@alumni.rice.edu: pageBreak resets
page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
Hi Joe,
It seems intuitive to me that page-count be absolute, and that \pageBreak
simply indicates where the page *must* break within those
Comment #5 on issue 884 by kie...@alumni.rice.edu: pageBreak resets
page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
That being said... If I understand your fix correctly, with 5 \pageBreak-s,
I can say
\paper { page-count = #'(1 3 2 2 1 3) }
and the score
Comment #6 on issue 884 by perpeduumimmobile: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
Thanks, Joe, works like a charm.
Is it reasonable to make page-count to automatically repeat the last item
of the list as necessary to get the n+1
Comment #7 on issue 884 by perpeduumimmobile: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
Thanks, Joe, works like a charm.
Is it reasonable to make page-count to automatically repeat the last item
of the list as necessary to get the n+1
Comment #8 on issue 884 by reinhold.kainhofer: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
Am Mittwoch, 16. Juni 2010, 14:45:10 schrieb lilyp...@googlecode.com:
I have changed the workings of page-count so that it interacts better with
Updates:
Status: Started
Comment #9 on issue 884 by joeneeman: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
Wow, I didn't realize this would be so controversial. The reason that it's
non-trivial to go back to the old behaviour is that it
Comment #10 on issue 884 by organsnyder: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
It seems to me like you're trying to account for someone trying to do
something stupid (no offense to anyone...). I think that the best solution
would be
Comment #11 on issue 884 by kie...@alumni.rice.edu: pageBreak resets
page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
I'd much prefer being able to say give me six pages, with explicit
breaks here and here.
+1
This is the way \pageTurn works [or should, in any
Updates:
Labels: -Priority-Medium Priority-Critical Regression
Comment #1 on issue 884 by brownian.box: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
http://lists.gnu.org/archive/html/lilypond-user/2010-06/msg1.html
2.12 produces
Status: Accepted
Owner: v.villenave
CC: nicolas.sceaux, joeneeman
Labels: Type-Defect Priority-Medium
New issue 884 by v.villenave: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
From Chris Snyder:
According to LNR 4.1.2, the page-count setting
27 matches
Mail list logo
