Comment #7 on issue 1967 by [email protected]: \partcombine and slurs produce
misleading warnings (when combining into chords)
http://code.google.com/p/lilypond/issues/detail?id=1967
I've checked with an old Ubuntu binary install. 2.12.thelatest does not
have the problem. 2.14.thelatest _has_ the problem. There is no point in
trying to place blame on the EventChord changes.
Looking at the partcombiner code, it has
a) been written predominantly in the LilyPond "don't ask, don't tell"
tradition regarding the comments particularly concerning the big picture,
and in a Goops style
b) it works at the stream event level
Now the EventChord changes have been done and installed at the music and
iterator level, with the explicit aim to generate the same stream events as
before. All regressions caused by that were in the area of _music_
expressions. The part combiner works with stream events. To the best of
my conscience and knowledge, it would be unaffected by the EventChord
changes since it never saw an EventChord before, and still doesn't.
So there is no particular reason to expect _me_ to track down and fix a bug
that has been introduced and present before my active time.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
