Am Sa., 6. Aug. 2022 um 17:15 Uhr schrieb Jean Abou Samra <jean@abou-samra.fr>:
>
> Le 06/08/2022 à 16:45, Werner LEMBERG a écrit :
> >> That said, there's a much simpler way. [...]
> > Your solution is ingenious. However, how on earth are we mere mortals
> > able to find that?
>
>
> Read the source, Luke :-)
roflmao
>
> Seriously, there is no way around that in this case -- as in many cases
> when it comes to Scheme coding, because the task is essentially to meddle
> with LilyPond internals.
>
> Obviously, I don't claim that this is something every user is supposed to
> be able to do.
Some remarks:
(1) `meta'
> \override TrillSpanner.meta.object-callbacks.side-support-elements = ...
I'd never thought overriding `meta' is possible at all.
Afaict, there is no example anywhere.
Overriding other meta-subproperties like `class'may result in
surprises, not tested, though.
<snip>
And cc-code is locked from the user.
cc code on the user's machine is locked from the user. But one can either browse the source on gitlab or savannah, or one can clone the git repository and get access to the source, even though you are not compiling the source. I recognize that this is challenging and difficult, but it is possible. I do it quite frequently now, since I don't have a development setup on my computer.
I say this not to disagree with your main points, with which I completely agree. But for someone who wants to look at the cc code, I thought it would be nice to mention the possibilities.
Thanks,
Carl