Carl Sorensen <[email protected]> writes: > On 7/6/16 5:07 AM, "Gilberto Agostinho" <[email protected]> wrote: > >> >>Is this a known bug? The only similar bug I found in the tracker is this >>one here <https://sourceforge.net/p/testlilyissues/issues/3766/> , but it >>seems to be a bit different than what I am reporting here. >> >>Cheers, >>Gilberto >> > > Why do you think issue 3766 is different from your observation? Both are > a collision between the tuplet bracket and the accidentals. It seems to > me they are the same thing (although the patch for issue 3766 was never > applied, as it didn't yet meet LilyPond coding standards).
I don't think the coding standards were concerned here. I put forward a counterexample to the underlying assumptions (which did not seem hard to fix, just remove some heuristic) and Mike did not pick up after that. It's not like we rarely have the situation of a patch getting lost in that stage when it meets the submitters requirements but he/she does not really feel like investing a lot of effort in it. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
