Dear Hans, this seems to have solved the problem, but now new ones have appeared. When compiling the file I get this very strange message: GNU LilyPond 2.24.4 (running Guile 2.2) Processing `toys.ly' Parsing...Guile used to use the wrong argument order for string-delete. This call to string-filter had the arguments in the wrong order. See SRFI-13 for more details. At some point we will remove this hack. ERROR: In procedure %resolve-variable: Unbound variable: %
Am Fr., 7. März 2025 um 22:34 Uhr schrieb Hans Aikema < [email protected]>: > > > > On 7 Mar 2025, at 21:30, Stefan Thomas <[email protected]> > wrote: > > > > > > Dear community. > > After upgrading to version 2.24.4. I get, after compiling a certain > file, the error message: > > fatal error: Not a markup command: fosterisk > > It must have to do with this code, I guess. Can it be updated? > > My gut feel without much knowledge would be: it's stricter now and doesn't > let you use a function that you did not-yet define. > > My first try if I would've run into it would be swapping the sequence of > defining the fosterisk ( #(define-markup-command... ) and the usage of it ( > #(let.... ) > > >
