lilypond-user
[Top][All Lists]
Advanced

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

Re: Automatic Lyric Extenders


From: Alexander Kobel
Subject: Re: Automatic Lyric Extenders
Date: Tue, 20 Dec 2016 11:04:01 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0

On 2016-12-20 02:44, Br. Samuel Springuel wrote:
On 2016-12-19 6:27 PM, Simon Albrecht wrote:
I actually meant using an include file like the attached and not
having to add the music function locally at all.

Beautiful - didn't know that this was possible at all.

#(set! toplevel-music-functions
       (cons (lambda (music parser) (autoextenders music))
         toplevel-music-functions))

When I add this to the bottom of autoextenders.ily I get the following
error: [...]
Based on memories of reading this list, and the hint about number of
arguments, I realized that the problem was because I'm using 2.19.53 and
the parser argument is no longer required.  Deleting that got things
working.  It should be noted that this was not something that convert-ly
run on autoextenders.ily caught; I had to do this manually.

I'm not surprised; I don't think that convert-ly touches Scheme code like that. Simplified version of the above:

#(set! toplevel-music-functions
       (cons autoextenders toplevel-music-functions))

I thought of using sed too, but thanks to Simon don't have to anymore.
What I was more concerned about, however, was the time needed to review
the results of the application to see if anything broke as a result.

I see.

After a quick review of the half-dozen or so examples I have entered for
this project so far, everything seem fine.

Great. Just out of curiosity (and because we need to pick a default of the equivalent variable for the release version at some point): which value for minimum-length did you prefer?


Cheers,
Alexander



reply via email to

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