<lilyp...@googlecode.com> wrote in message
news:8-9567054385019064696-16094765952880031725-lilypond=googlecode....@googlecode.com...
Comment #8 on issue 1967 by gra...@percival-music.ca: \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
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
