Werner LEMBERG writes:
>>> I don't think LilyPond guarantees a particular order of events
>>> occuring at the same moment, but I agree that wrapping them should
>>> not change the order. An issue has been created to track this
>>
>> But the regression test script-stack-order.ly is quite
>> I don't think LilyPond guarantees a particular order of events
>> occuring at the same moment, but I agree that wrapping them should
>> not change the order. An issue has been created to track this
>
> But the regression test script-stack-order.ly is quite explicit
> about the order being
Kevin Barry wrote:
I don't think LilyPond guarantees a particular
order of events occuring at the same moment, but I agree that wrapping
them should not change the order.
An issue has been created to track this
Thanks.
But the regression test script-stack-order.ly is quite explicit about
On Sat, Mar 13, 2021 at 05:19:49PM +0100, Robin Bannister wrote:
> Hallo there
>
> I noticed this while trying to make an MWE for a different problem.
>
> Maybe it counts as a limitation rather than a bug?
Hi Robin,
Thank you for the report. I don't think LilyPond guarantees a particular
order
Hallo there
I noticed this while trying to make an MWE for a different problem.
Maybe it counts as a limitation rather than a bug?
Cheers,
Robin
% MWE for post-event ordering via event-function and wrapper
\markup #(lilypond-version)
ts-first-second =
#(define-event-function () ()
#{