bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1967 in lilypond: \partcombine and slurs produce misleadingwar


From: Phil Holmes
Subject: Re: Issue 1967 in lilypond: \partcombine and slurs produce misleadingwarnings (when combining into chords)
Date: Tue, 14 Feb 2012 10:51:48 -0000

<address@hidden> wrote in message news:address@hidden

Comment #8 on issue 1967 by address@hidden: \partcombine and slurs produce misleading warnings (when combining into chords)
http://code.google.com/p/lilypond/issues/detail?id=1967

I agree that this doesn't seem to have anything to do with EventChord changes, so of course David is no "on the hook" for this.

There are three avenues of approach:
- test 2.13.x binary releases to find the cause of this regression.
- look at the commit history for the relevant file(s) between 2.12.3 and 2.14.2.
- ignore the history and just look for the bug in the current code.

Slightly oddly, I get the warning in 2.14.2 but not 2.14.0 and not in any 2.13.x releases

This is using \partcombine instead of \partcombineUp

--
Phil Holmes
Bug Squad






reply via email to

[Prev in Thread] Current Thread [Next in Thread]