Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice
Comment #1 on issue 1770 by reinhold...@gmail.com: \displayLilyMusic causes error with \oneVoice http://code.google.com/p/lilypond/issues/detail?id=1770 The problem seems to lie in the handling of RevertProperty. However, I must say that the output for 2.14 is totally unhelpful for debugging the problem. It does not tell you where the problem occurred and which function call caused it. Is there any way to revert the error output to the output of 2.12, which is really great for debugging? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1725 in lilypond: DynamicTextSpanner collides with DynamicText
Comment #2 on issue 1725 by x.sche...@gmail.com: DynamicTextSpanner collides with DynamicText http://code.google.com/p/lilypond/issues/detail?id=1725 Thanks for the workaround Keith. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1724 - 620 : workaround?
[Sorry for late follow-up, I was on holiday. :-) ] Hi Neil, I see you merged issue 1724 : DynamicTextSpanner inside Dynamics context are shifted due to pedal into issue 620 : It should be possible to specify more specific spanner bounds.. I was wondering if you (or someone else) would have maybe a workaround I could use in order to have a fairly good output for the code attached to #1724 ? http://code.google.com/p/lilypond/issues/detail?id=1724 Issue 1724 is really annoying for me since it totally demolish the advantages of using the Dynamics context. Yes, we have the dynamics correctly aligned vertically (i.e. centered between the two staves of PianoStaff) but due to issue 1724 (620) the DynamicText and DynamicTextSpanner are shifted left irregularly, which results in really bad horizontal alignment (- poor output !). Any help would be greatly appreciated. Thanks in advance! Cheers, Xavier PS : Please note that since issue 620 has no lilypond code showing the consequences of this issue, it is difficult for a lambda user to understand it, hence IMHO the several duplicate report of this issue. -- Xavier Scheuer x.sche...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 896 in lilypond: When used after \tag, \partcombine may fail to print notes
Comment #2 on issue 896 by reinhold...@gmail.com: When used after \tag, \partcombine may fail to print notes http://code.google.com/p/lilypond/issues/detail?id=896 partcombine does its job (deciding how to distribute the note events to the up/down/combined voices) long before the keepWithTag is run. So, to partcombine the music looks like: e4 e4 f g a b r c r Unfortunately, later on the second e4 is removed, so the decisions of the part-combiner are off by a quarter. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 34 in lilypond: Grace synchronization
Comment #14 on issue 34 by reinhold...@gmail.com: Grace synchronization http://code.google.com/p/lilypond/issues/detail?id=34 I did a little digging and the issue is that all \set commands (like the clef) and all other events (like KeyEvent) are treated as if they occurred together with the first note (and that problem lies deeper than the Sequential_iterator's handling of grace notes!). I.e. if you have: Voice 1: \clef bass \grace c8 d4 Voice 2: \clef bass d4 Then in Voice 1, the clef properties (clefGlyph and the like) will be set at moment 0G-1/8, while in Voice 2, they will be set only at moment 0G. Similarly, all key events will be assigned the moment of the first note... Now, the iterators and then the engravers go through the music one moment at a time, so the order of things is: -) moment 0G-1/8 : only voice 1 creates a clef and the grace note -) moment 0 : voice 1 creates the d4, while voice 2 changes the clef and creates a d4. However, in my eyes we need to distinguish the events at each moment. Basically, we have three different types of events: 1) events that should be processed at the very beginning of each moment (before grace notes are handled) 2) grace notes (i.e. notes that appear before the real content of the moment), possibly also including some \set command, which should not mess up things 3) normal notes In other words, we need to find a way to process key/clef/barlines (in particular all SetEvents) etc. before all grace notes. One approach might be to assign a moment like 0G-inf to them, so they will be processed before all grace notes. Or does anyone have a better idea where to start? Cheers, Reinhold ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice
Updates: Status: Started Owner: reinhold...@gmail.com Comment #2 on issue 1770 by reinhold...@gmail.com: \displayLilyMusic causes error with \oneVoice http://code.google.com/p/lilypond/issues/detail?id=1770 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1744 in lilypond: \once \set behavior should be documented
Comment #1 on issue 1744 by reinhold...@gmail.com: \once \set behavior should be documented http://code.google.com/p/lilypond/issues/detail?id=1744 Issue 153 is a valid request, and I think that \once\set should work just like described there (i.e. revert to the value before the \once\set). Adding documentation about this limitation is just a workaround for now, until we fix issue 153 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account
Comment #7 on issue 155 by reinhold...@gmail.com: \parenthesize does not take accidentals into account http://code.google.com/p/lilypond/issues/detail?id=155 Issue 868 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice
Updates: Labels: Patch-new Comment #3 on issue 1770 by reinhold...@gmail.com: \displayLilyMusic causes error with \oneVoice http://code.google.com/p/lilypond/issues/detail?id=1770 Patch up for review: http://codereview.appspot.com/4805043 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly
Comment #6 on issue 1732 by reinhold...@gmail.com: occasional segfault when compiling input/regression/midi/key-initial.ly http://code.google.com/p/lilypond/issues/detail?id=1732 The error message throw from within critical section. indicates that this is a problem somewhere in threaded GUILE (they are using critical sections instead of finer-grained mutexes). In particular, a (throw ...) function was called in guile, while guile was in a critical section (i.e. one where no error should occur). In that case, guile's libguile/throw.c simply exists. Unfortunately, it does not print out the exception that was thrown, so it's really hard to track down where the problem lies... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font
Comment #20 on issue 1752 by x.sche...@gmail.com: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 For what it counts, I still do not see the need to change the current treble clef. But IMHO your last proposal is far more acceptable than your first design. As I said, I'm not a font specialist and I won't vote against your work. Count me as neutral. If the majority prefers the new suggestion, then let's switch to it. It won't be possible to please everybody. Again, thanks for your work Janek. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 868 in lilypond: \parenthesize does not take dotted notes into account
Updates: Status: Duplicate Mergedinto: 155 Comment #2 on issue 868 by reinhold...@gmail.com: \parenthesize does not take dotted notes into account http://code.google.com/p/lilypond/issues/detail?id=868 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1724 - 620 : workaround?
On 20 July 2011 13:27, Xavier Scheuer x.sche...@gmail.com wrote: I was wondering if you (or someone else) would have maybe a workaround I could use in order to have a fairly good output for the code attached to #1724 ? http://code.google.com/p/lilypond/issues/detail?id=1724 Let me think about it for a bit. I have an idea using a scheme engraver which might work. PS : Please note that since issue 620 has no lilypond code showing the consequences of this issue, it is difficult for a lambda user to understand it, hence IMHO the several duplicate report of this issue. You're welcome to add snippets to it rather than relying on the links to the merged issues (we could also mention the Dynamics context in the issue title). Cheers, Neil ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Status: Fixed Labels: -Patch-review -CD-110718 fixed_2_15_6 backport Comment #8 on issue 1695 by n.putt...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 bebd93c2dd0d7363f311d912ec1ed1f7dfcb36ba ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes
Comment #5 on issue 1735 by x.sche...@gmail.com: modifying default behaviour of tremolo slashes http://code.google.com/p/lilypond/issues/detail?id=1735 Please keep current settings (i.e. rectangular, parallel-to-the-beam tremolos) as default behaviour. Joe said he took this as default because that's what most of his scores have and according to my personal experience, the current lily settings looks far more familiar to scores I have played than the new proposed default. The last score I played is Beethoven's Piano Concerto No.5 and as you can see on IMSLP in the Violin I part (first page) http://imslp.org/wiki/Piano_Concerto_No.5,_Op.73_%28Beethoven,_Ludwig_van%29 http://imslp.info/files/imglnks/usimg/f/f2/IMSLP19342-PMLP03875-Beethoven_Piano_Concerto_5_V1.pdf this edition by Breitkopf Härtel uses rectangular, parallel-to-the-beam tremolos (just as current lily settings). IMHO we should not blindly follow Elaine Gould. Eventually it would be great if someone took the time to study what are the practices of renowned publisher's editions. Or maybe try a little survey on lilypond-user. Maybe the new proposed constant, non-rectangular could be the default for RhythmicStaff (but we should ask some percussionists about it) Thanks in advance and thanks for your work Janek, it is nice to have such a feature. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice
Comment #4 on issue 1770 by carl.d.s...@gmail.com: \displayLilyMusic causes error with \oneVoice http://code.google.com/p/lilypond/issues/detail?id=1770 This shouldn't be Critical -- it's not a segfault. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Updates: Labels: -backport fixed_2_14_2 Comment #9 on issue 1695 by carl.d.s...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 Backported ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1771 in lilypond: Nested reverts fail for properties which aren't set as defaults in define-grobs.scm
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1771 by n.putt...@gmail.com: Nested reverts fail for properties
which aren't set as defaults in define-grobs.scm
http://code.google.com/p/lilypond/issues/detail?id=1771
From the regtest property-nested-revert.ly:
\version 2.15.6
\relative c' {
f2 \glissando c
\override Glissando #'bound-details #'right #'Y = #4
f2 \glissando c |
\override Glissando #'bound-details #'left #'Y = #-6
f2 \glissando c
\revert Glissando #'(bound-details right Y)
f2 \glissando c
\revert Glissando #'(bound-details left Y)
f2 \glissando c
}
Neither \revert restores the default behaviour unless the initial overrides
are defined in Glissando's bound-details defaults inside define-grobs.scm.
This is directly caused by the fix for issue 1063,
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=4ea5963dd6b5289e57454bd2702b9527c06d6001,
but slipped through since the regression test is flawed in using
glissandos; they have no extent, so don't show up in regtest comparisons.
Attachments:
lily-ec5de296.png 3.5 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break (bounds of spanner are invalid)
Updates: Labels: -Patch-review Patch-new Comment #4 on issue 1433 by reinhold...@gmail.com: \breakDynamicSpan breaks with \break (bounds of spanner are invalid) http://code.google.com/p/lilypond/issues/detail?id=1433 Revised patch is up at http://codereview.appspot.com/4630070/ This new version now correctly handles the ordering of \breakDynamicSpan and \ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break (bounds of spanner are invalid)
Updates: Labels: -Patch-new Patch-review Comment #5 on issue 1433 by pkx1...@gmail.com: \breakDynamicSpan breaks with \break (bounds of spanner are invalid) http://code.google.com/p/lilypond/issues/detail?id=1433 Make is fine, the same reg test that showed a difference last time now shows that the text 'dim...' has been replaced by hairpins, is this what is wanted? See attached. Attachments: Issue_4630070.png 49.5 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1768 in lilypond: Tremoli can collide with flags in tight spacing situations.
Updates: Labels: -Patch-new Patch-needs_work Comment #5 on issue 1768 by pkx1...@gmail.com: Tremoli can collide with flags in tight spacing situations. http://code.google.com/p/lilypond/issues/detail?id=1768 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break
Updates: Labels: -Patch-new Patch-review Comment #5 on issue 1259 by pkx1...@gmail.com: DynamicTextSpanner #'style = #'none doesn't work over \break http://code.google.com/p/lilypond/issues/detail?id=1259 Sorry I'm getting confused now. The last comment refers to a Rietveld twhich itself refers to Tracker issue 1433. If this one Rietveld is for both Trackers then ok. but see my comment http://code.google.com/p/lilypond/issues/detail?id=1433#c5 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1744 in lilypond: \once \set behavior should be documented
Comment #4 on issue 1744 by reinhold...@gmail.com: \once \set behavior should be documented http://code.google.com/p/lilypond/issues/detail?id=1744 Just wait until my patch for issue 153 is pushed, then \once\set behaves just as expected and we don't need to document anything. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break
Comment #6 on issue 1259 by reinhold...@gmail.com: DynamicTextSpanner #'style = #'none doesn't work over \break http://code.google.com/p/lilypond/issues/detail?id=1259 That patch on Rietveld is for both issue 1433 and issue 1259. Both are caused by the same problem. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 34 in lilypond: Grace synchronization
lilypond at googlecode.com writes: Comment #14 on issue 34 by reinhold...@gmail.com: Grace synchronization http://code.google.com/p/lilypond/issues/detail?id=34 However, in my eyes we need to distinguish the events at each moment. Basically, we have three different types of events: 1) events that should be processed at the very beginning of each moment (before grace notes are handled) 2) grace notes (i.e. notes that appear before the real content of the moment), possibly also including some \set command, which should not mess up things 3) normal notes In other words, we need to find a way to process key/clef/barlines (in particular all SetEvents) etc. before all grace notes. One approach might be to assign a moment like 0G-inf to them, so they will be processed before all grace notes. I think that is a promising approach. I looked through the code thinking about this issue two days ago, and began to look for a way to default-initialize the grace_part_ of a Moment to something that would sort before any defined value of grace_part_. I do not know enough Scheme to know if Rational grace_part_ = -1 / 0 is guaranteed to work as -inf. It looks like most events should have effectively -inf for the grace_part_ of their timing. The new method would need to take over the job that create_grace_fixup_list() tries to do. I am still figuring out how the list is created. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font
Updates: Labels: -Patch-review Patch-needs_work Comment #21 on issue 1752 by n.putt...@gmail.com: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 Patch set 3 needs more work: clef selection is broken for all clefs apart from treble if 'old style is set. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1390 in lilypond: Tied acciaccaturas should not be printed with a slur
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_6 Comment #5 on issue 1390 by reinhold...@gmail.com: Tied acciaccaturas should not be printed with a slur http://code.google.com/p/lilypond/issues/detail?id=1390 Pushed to git. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1507 in lilypond: weird linebreaks in song output
Updates: Labels: -Patch-review -CD-110718 Patch-needs_work Comment #7 on issue 1507 by colinpkc...@gmail.com: weird linebreaks in song output http://code.google.com/p/lilypond/issues/detail?id=1507 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes
Updates: Labels: CD-110722 Comment #6 on issue 1735 by colinpkc...@gmail.com: modifying default behaviour of tremolo slashes http://code.google.com/p/lilypond/issues/detail?id=1735 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1727 in lilypond: Adds glissando stems to lilypond
Updates: Labels: -Patch-review Patch-needs_work Comment #1 on issue 1727 by colinpkc...@gmail.com: Adds glissando stems to lilypond http://code.google.com/p/lilypond/issues/detail?id=1727 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice
Updates: Labels: CD-110722 Comment #7 on issue 1770 by colinpkc...@gmail.com: \displayLilyMusic causes error with \oneVoice http://code.google.com/p/lilypond/issues/detail?id=1770 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
Updates: Labels: -Patch-review Patch-needs_work Comment #11 on issue 1767 by colinpkc...@gmail.com: Feta font - change breve vertical lines http://code.google.com/p/lilypond/issues/detail?id=1767 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 153 in lilypond: \once \set fails to restore previous setting
Updates: Status: Started Owner: reinhold...@gmail.com Labels: Patch-new Comment #12 on issue 153 by reinhold...@gmail.com: \once \set fails to restore previous setting http://code.google.com/p/lilypond/issues/detail?id=153 Patch is up for review at: http://codereview.appspot.com/4810042 (This also fixes #1744) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break
Updates: Labels: -Patch-review Patch-new Comment #4 on issue 1259 by reinhold...@gmail.com: DynamicTextSpanner #'style = #'none doesn't work over \break http://code.google.com/p/lilypond/issues/detail?id=1259 Revised patch is up at http://codereview.appspot.com/4630070/ This new version now correctly handles the ordering of \breakDynamicSpan and \ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode
Updates: Labels: -Patch-review Patch-needs_work Comment #11 on issue 1688 by colinpkc...@gmail.com: New half-closed hihat symbol for drum mode http://code.google.com/p/lilypond/issues/detail?id=1688 Neil has raised a couple of concerns. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1491 in lilypond: git-cl hangs when uploading patches due to bad mime-type
Comment #3 on issue 1491 by percival.music.ca: git-cl hangs when uploading patches due to bad mime-type http://code.google.com/p/lilypond/issues/detail?id=1491 judging from http://codereview.appspot.com/4819041/ this is an issue for .ps files as well. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1705 in lilypond: New breve rest with ledger lines
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_6 Comment #5 on issue 1705 by n.putt...@gmail.com: New breve rest with ledger lines http://code.google.com/p/lilypond/issues/detail?id=1705 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1744 in lilypond: \once \set behavior should be documented
Comment #3 on issue 1744 by pkx1...@gmail.com: \once \set behavior should be documented http://code.google.com/p/lilypond/issues/detail?id=1744 Is this a bug? If so we don't document bugs as a rule. If it is just a limitation of the feature then can someone give me some guidance on what they want and where and I'll get a patch up. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice
Updates: Labels: -Priority-Critical Priority-High Comment #6 on issue 1770 by n.putt...@gmail.com: \displayLilyMusic causes error with \oneVoice http://code.google.com/p/lilypond/issues/detail?id=1770 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1695 in lilypond: Clef change placed outside score
Comment #10 on issue 1695 by carl.d.s...@gmail.com: Clef change placed outside score http://code.google.com/p/lilypond/issues/detail?id=1695 Backported ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
