H. S. Teoh <hsteoh <at> quickfur.ath.cx> writes: > % Arguably, using \tag with \partcombine is a bad idea, since it can > % easily result in constructs that are probably not representable in a > % way that would make a subsequent \removeWithTag work correctly, but > % Lilypond should at least give a warning and/or reject such input > % instead of generating wrong output.
It looks like this is already tracked. https://code.google.com/p/lilypond/issues/detail?id=896 _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
