Re: How to delete a created Glissando without impact on line break?
Dan Eble <[email protected]> Sun, 28 Jun 2026 13:28:43 -0400
| Newsgroups | gmane.comp.gnu.lilypond.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2026-06-28 08:33, Thomas Morley wrote: > > To fix #6946 it would be sufficient to create only those Glissando > grobs really needed, then there would be no need to delete some of > them afterwards. > There seem to be some conditions for that purpose in the original > cc-engraver, but I don't understand them sufficiently. Harm, Issue #6946 seems to be a recurrence of issue #1639, which was fixed in b8dfb88ca356cdde12cccb4cf57ecc64397c137b. That change defers grob suicide until other engravers have had the opportunity to acknowledge the end of the spanner. Probably, the best response would be to update the Scheme implementation of Glissando_engraver to defer grob suicide similarly. Since the issue is a regression, the change would ideally be kept minimal so that it could easily be back-ported to 2.26. Secondarily, it might be helpful to make Spanner_break_forbid_engraver more robust in the presence of dead grobs. I'll investigate this part. -- Dan