Updates:
Labels: fixed_2_14_2
Comment #9 on issue 1618 by carl.d.s...@gmail.com: unpredictable placement
of rests
http://code.google.com/p/lilypond/issues/detail?id=1618
Backported
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Updates:
Status: Verified
Comment #8 on issue 1618 by philehol...@googlemail.com: unpredictable
placement of rests
http://code.google.com/p/lilypond/issues/detail?id=1618
(No comment was entered for this change.)
___
bug-lilypond mailing
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_0
Comment #7 on issue 1618 by k-ohara5...@oco.net: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
patch pushed in 1edd0
___
Comment #5 on issue 1618 by percival.music.ca: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
Amazing work as always. I can confirm the clean regtests, and I've
uploaded the patch here:
http://codereview.appspot.com/4441066/
Updates:
Labels: -Patch-new Patch-review
Comment #6 on issue 1618 by k-ohara5...@oco.net: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
I resolved my connection problem, and uploaded the patch and a regtest at
Comment #3 on issue 1618 by percival.music.ca: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
I'm happy with this rationale.
Another note on valgrind: you _can_ use valgrind on lilypond, but in
addition to all the memory errors it finds with guile
Comment #1 on issue 1618 by percival.music.ca: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
I think it happened earlier than 2.13.48 -- maybe even before 2.12 or 2.10,
meaning that it's not Critical. I tried to do a bisect, but I ended up
You can run valgrind on lilypond. You just need to disable the
warnings regarding garbage collection.
On Sun, Apr 17, 2011 at 5:24 AM, lilyp...@googlecode.com wrote:
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1618 by percival.music.ca: unpredictable
Updates:
Labels: -Priority-Critical Priority-High
Comment #2 on issue 1618 by k-ohara5...@oco.net: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
Quite possibly the problem existed in 2.13.48, and my testing missed it.
Testing for
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1618 by percival.music.ca: unpredictable placement of rests
http://code.google.com/p/lilypond/issues/detail?id=1618
This is split from issue 1609 (that issue was specifically about the
problem we saw in
10 matches
Mail list logo
