Issue 253 in project lilypond

Issue 253: 2.11.13 bus error http://code.google.com/p/lilypond/issues/detail?id=253 Comment #4 by joeneeman: I've fixed this error, but I don't think it is the same as the original one. First of all, it was introduced long before 2.11.9 and secondly, it should only apply to very short scores.

Arpeggio collision

I see that issue 10 is closed (http://code.google.com/p/lilypond/issues/detail?id=10). However, I'm still seeing similar behavior. The attached is from the actual score. If I take out the accidentals it looks right. I can also remove the acciacatura from the low voice to keep the arpeggio on the c

Issue 253 in project lilypond

Issue 253: 2.11.13 bus error http://code.google.com/p/lilypond/issues/detail?id=253 Comment #3 by hanwenn: Hi Joe, can you have a look? In general, it is always better to not assert() and use programming_error() instead. Issue attribute updates: Cc: joeneeman Labels: -Prior

EasyHeads fails

Easyheads appears to be broken in 2.10.12 \version "2.10.12") \paper { ragged-right=##t} { \setEasyHeads c' d' e' f' } produces a single notehead with no stem. (see attached png) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/

Issue 253 in project lilypond

Issue 253: 2.11.13 bus error http://code.google.com/p/lilypond/issues/detail?id=253 Comment #2 by trevorbaca: Aha. Extremely minimal example showing glissando over page break to be the culprit: %%% BEGIN %%% \version "2.11.13" \new Staff { c'1 \glissando \pageBreak d'1 } %%% END %%%

Issue 251 in project lilypond

Issue 251: subdivideBeams and automatic beaming http://code.google.com/p/lilypond/issues/detail?id=251 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC field

Issue 250 in project lilypond

Issue 250: cresc extends to follow \mark instead of stopping at \> http://code.google.com/p/lilypond/issues/detail?id=250 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in th

Issue 230 in project lilypond

Issue 230: segfault 2.11.10 http://code.google.com/p/lilypond/issues/detail?id=230 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or

Issue 222 in project lilypond

Issue 222: measure "numbers" in XML aren't actually numbers http://code.google.com/p/lilypond/issues/detail?id=222 Comment #10 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owne

Re: lilypond-2.10.12 does not configure with mftrace 1.1.19

Jean Bréfort normalesup.org> writes: > > Configure fails with: > ERROR: Please install required programs: mftrace >= 1.1.19 (installed: > 1.1) > > but mftrace --version gives: > mftrace 1.1.19 > > I could trace the issue to STEPMAKE_GET_VERSION which drops the micro > version, so requesting 1

Issue 252 in project lilypond

Issue 252: collision beam notehead in polyphony http://code.google.com/p/lilypond/issues/detail?id=252 Comment #2 by gpermus: Not your fault; I searched for this twice, because I had a vague memory of this bug. Apparently the google code search makes a distinction between plural or singular word

Issue 254 in project lilypond

Issue 254: ./configure chokes on mftrace-1.1.19 (bug in STEPMAKE_GET_VERSION) http://code.google.com/p/lilypond/issues/detail?id=254 Comment #3 by [EMAIL PROTECTED]: Sorry, hit the wrong button there. Obviously, you'll want to update the m4 file the aclocals are generated from. Attachments:

Issue 254 in project lilypond

Issue 254: ./configure chokes on mftrace-1.1.19 (bug in STEPMAKE_GET_VERSION) http://code.google.com/p/lilypond/issues/detail?id=254 Comment #2 by [EMAIL PROTECTED]: This is the alternate, more consistent patch I mentioned above: -- You received this message because you are listed in the owner

Issue 254 in project lilypond

Issue 254: ./configure chokes on mftrace-1.1.19 (bug in STEPMAKE_GET_VERSION) http://code.google.com/p/lilypond/issues/detail?id=254 Comment #1 by [EMAIL PROTECTED]: This is the patch we're using in Gentoo: Attachments: lilypond-2.10.8-version.patch 1.1 KB -- You received this messa

Issue 254 in project lilypond

Issue 254: ./configure chokes on mftrace-1.1.19 (bug in STEPMAKE_GET_VERSION) http://code.google.com/p/lilypond/issues/detail?id=254 New issue report by [EMAIL PROTECTED]: checking for makeinfo... (cached) makeinfo checking makeinfo version... 4.8 configure: creating ./config.status config.status:

Issue 252 in project lilypond

Issue 252: collision beam notehead in polyphony http://code.google.com/p/lilypond/issues/detail?id=252 Comment #1 by Carl.D.Sorensen: I think that this is the same bug as issue #37. I'm sorry for not recognizing this sooner. Carl Sorensen -- You received this message because you are listed

Issue 202 in project lilypond

Issue 202: merge-differently-headed should work for >2 voices http://code.google.com/p/lilypond/issues/detail?id=202 Comment #6 by Carl.D.Sorensen: This item can now be closed, as far as I can tell. I've got a snippet that demonstrates a workaround, and might possibly be added to the manual. He

Issue 253 in project lilypond

Issue 253: 2.11.13 bus error http://code.google.com/p/lilypond/issues/detail?id=253 Comment #1 by trevorbaca: Downloading and testing each build in sequence (starting at 2.11.7 and going forward) reveals that the bus error first showed up in 2.11.10; ie, 2.11.7, .8 and .9 are all fine but .10, .

Issue 253 in project lilypond

Issue 253: 2.11.13 bus error http://code.google.com/p/lilypond/issues/detail?id=253 New issue report by trevorbaca: 2.11.13 includes some sort of bus error that 2.11.7 does not. GNU LilyPond 2.11.13 Processing `/Users/trevorbaca/Documents/music/lilypond/pictures/0239.ly' Parsing... Interpreting m