lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Automatic lyric extenders


From: Urs Liska
Subject: Re: Automatic lyric extenders
Date: Wed, 14 Dec 2016 11:03:15 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0


Am 14.12.2016 um 10:45 schrieb Alexander Kobel:
> On 2016-12-14 07:50, Knut Petersen wrote:
>> Hi Alexander!
>>
>>> add-lyric-extenders =
>>> #(define-music-function (parser location lyrics) (ly:music?)
>>
>> You don't need "parser location".
>
> Hi Knut,
>
> I think I do - see the post on lily-devel. AFAIK, the type check
> (here: ly:music?) is applied to the third argument of the function.
> Only 90 % sure though, can't test right now.
>
> But you're right that I don't /use/ parser and location, so I could
> also use a plain define without harm.

"parser location" is not used anymore in general, and I assume it will
be removed one day.
So this really should be

#(define-music-function (lyrics)(ly:music?)

(if ly:music? is the right predicate for lyrics, that is).

(if you have to access the parser or the location you can by now use
(*parser*) and (*location*) anywhere without having to explicitly add it
to the function signature (one of the great improvements in 2.19)

Urs

>
>
> Cheers,
> Alexander
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user




reply via email to

[Prev in Thread] Current Thread [Next in Thread]