Lukas-Fabian Moser <[email protected]> writes:

> Am 30.09.26 um 15:27 schrieb David Kastrup:
>> \after is written in a manner where you can just write
>>
>> \after { 2. 16 } ->
>>
>> and it will supply the <> on its own.  This is done in a "cute" manner
>> using a #{ ... #} construct that can be parsed in several different
>> manners.
> Ah yes, I forgot. Thanks for reminding me/us!
>>    I think that I might have posted a variant of this to the
>> mailing lists at some point, with it getting scavenged into LilyPond
>> later.
>
> ... the scavenger would have been me:
> https://gitlab.com/lilypond/lilypond/-/merge_requests/933
>
>> I think I'll back out the cuteness from LilyPond's internals, though,
>> and stop using #{ ... #} here.  That may make it more obvious to the
>> reader of the code that supplying one's own <> is not needed.
>
> I'm looking forward (and curious) to seeing that change!

It was a mistake.  If I hadn't done that, I'd not have noticed that
\displayLilyMusic needed an update for the new functionality anyway,
which would have turned this into Someone Else's Problemâ„¢ to be
discovered at a later point in time.

-- 
David Kastrup

Reply via email to