Le dimanche 02 avril 2023 à 18:45 -0400, Dan Eble a écrit :
> On Apr 2, 2023, at 14:39, Kevin Barry wrote:
> >
> > On Sun, 2 Apr 2023 at 19:31, Jean Abou Samra wrote:
> > > I can do
> > >
> > > (define-public grob-interpret-markup ly:grob-interpret-markup)
> > >
> > > like we already have for
On Apr 2, 2023, at 14:39, Kevin Barry wrote:
>
> On Sun, 2 Apr 2023 at 19:31, Jean Abou Samra wrote:
>> I can do
>>
>> (define-public grob-interpret-markup ly:grob-interpret-markup)
>>
>> like we already have for assoc-get aka ly:assoc-get, but it seems
>> clumsy.
>
> That is what I would do.
Le dimanche 02 avril 2023 à 20:31 +0200, Jean Abou Samra a écrit :
> We would need to rename those few for which both a ly: and a non-ly:
> variant exist (I'm thinking about
> (ly:)side-position-interface:y-aligned-side.)
PS: Here is the complete list of functions which would conflict with
On Sun, 2 Apr 2023 at 19:31, Jean Abou Samra wrote:
> I can do
>
> (define-public grob-interpret-markup ly:grob-interpret-markup)
>
> like we already have for assoc-get aka ly:assoc-get, but it seems
> clumsy.
That is what I would do.
Kevin
I am writing a patch (related to all the recent talks on font selection)
where I want to have `grob-interpret-markup` written in C++. I can
of course define it with LY_DEFINE, except that this makes it named
ly:grob-interpret-markup instead.
I can do
(define-public grob-interpret-markup ly:grob-i
