Phil Holmes <mail <at> philholmes.net> writes: > Could you check it with 13.60 or .61 to confirm it was wrong in a previous > version? If it was, I assume it was a bug but that it's fixed in a > development version. > Phil, Confirming that your example comes out wrong with 2.13.61 as released. It starts coming out right with the patch that fixes issue 1632, so we can consider this the same bug as 1632.
_______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
