Issue 253 in project lilypond

Issue 253: 2.11.13 bus error http://code.google.com/p/lilypond/issues/detail?id=253 Comment #11 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_15 -- You received this message because you are listed in the owner

Issue 135 in project lilypond

Issue 135: markup on spacer rests doesn't obey \emptyText http://code.google.com/p/lilypond/issues/detail?id=135 Comment #5 by hanwenn: removed inspection of X-extent of papercolumn in this case. Issue attribute updates: Status: Fixed Labels: fixed_2_11_16 -- You received this

URL not active in the footer

I'm not top posting. \version 2.10.14 \paper { } \header { title = URL not active in footer copyright = Creative Commons Attribution-ShareAlike 2.5 % These are headers used by the Mutopia Project % http://www.mutopiaproject.org/

Re: URL not active in the footer

I've discovered another strange thing: if move your cursor into the upper-left corner, there is an invisible but active link (the cursor changes to a hand and upon click it opens the URL) Philippe Hézaine írta: I'm not top posting. \version 2.10.14 \paper { } \header {

Melismata Terminate Early

Rests embedded within melismata cause extender lines to terminate at the point of rest. An example is below; it's rather complex (it's real music, albeit truncated for reporting), but the point demonstrated is simple. Running off 2.11.x, Mac OS X. \include english.ly theVoice = \relative

Re: Melismata Terminate Early

Er, sorry, a bump up to .15 fixed this problem. Ignore. Will On Feb 1, 2007, at 4.55 PM, Will Oram wrote: Rests embedded within melismata cause extender lines to terminate at the point of rest. An example is below; it's rather complex (it's real music, albeit truncated for reporting), but

Re: OoolilyPond

I am not top posting I had exactly the same error with the german version 2.02 of OpenOffice and version 2.11.x of LilyPond - then I upgraded to OOo 2.3 and downgraded to LP 2.10.14 and now it's perfect - very nice little application! Santé! Luc

Issue 263 in project lilypond

Issue 263: false tupletSpannerDuration produces bracket until end of piece http://code.google.com/p/lilypond/issues/detail?id=263 New issue report by gpermus: % if #(ly:make-moment) is a duration too large to hold the % \times, the tuplet bracket is extended until the end of the score.

Re: tupletSpannerDuration bug

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=263 Cheers, - Graham Tuukka Verho wrote: My apologies - I had changed the tupletSpannerDuration to 1/8 from 1/4 for testing purposes and didn't remember to change it back. This code demostrates the bug: \version 2.11.0

Issue 264 in project lilypond

Issue 264: url-link puts click area in wrong location http://code.google.com/p/lilypond/issues/detail?id=264 New issue report by hanwenn: I've discovered another strange thing: if move your cursor into the upper-left corner, there is an invisible but active link (the cursor changes to a hand

Re: URL not active in the footer

Bertalan Fodor escreveu: I've discovered another strange thing: if move your cursor into the upper-left corner, there is an invisible but active link (the cursor changes to a hand and upon click it opens the URL) Philippe Hézaine írta: I'm not top posting. \version 2.10.14

Issue 263 in project lilypond

Issue 263: false tupletSpannerDuration produces bracket until end of piece http://code.google.com/p/lilypond/issues/detail?id=263 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_10_16 fixed_2_11_16 -- You

Issue 265 in project lilypond

Issue 265: accidental too close to left bar line (bar line padding problem?) http://code.google.com/p/lilypond/issues/detail?id=265 New issue report by gpermus: % this problems looks familiar, but I can't find it in the issue search. :( \version quot;2.11.15quot; \paper{ ragged-right=##t }

Re: Accidentals too close to barline

Maximilian Albert wrote: I know that Frédéric Chiasson has already reported similar (maybe the same) issues. But I felt that a truly _minimal_ example might still be helpful. If it is not, please simply ignore this message. Thanks for the report. Do you know what bug number this issue got? I

2.11.15 debug help / detached beam

I'm getting this in a file that used to compile pre 2.11.15: Preprocessing graphical objects... programming error: no skylines for alignment-child continuing, cross fingers Segmentation fault I have the problem somewhat narrowed down to a couple of measures. Is there a way I can make it spit