James <p...@gnu.org> writes: > On Mon, 04 Sep 2017 08:38:02 +0200 > David Kastrup <d...@gnu.org> wrote: > >> Dan Eble <d...@faithful.be> writes: >> >> > So difficult to do anything about that it’s not worth tracking. >> > Very well. >> >> I don't know whether we have an issue entry for this or not. > > No I don't think we do.
If we did, I doubt it would end up as anything but wontfix since the payout for defining and guaranteeing a certain behavior in this case will likely be dwarfed by effort and regressions. I mean, I am usually in favor of making LilyPond do "the expected thing" but the expected thing here is rather hard to define given the lyricsto semantics. If we manage to do so, I'd rather suggest starting with making melisma-related overrides not act one step later than expected: I think this is closely related though not quite the same. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
