Re: Shortcut for \repeat unfold

[Jean Abou Samra]

Le 27/09/2021 à 23:52, David Kastrup a écrit :
> Jean Abou Samra <jean@abou-samra.fr> writes:
>
> > is not entirely true: once a function is defined, it can be
> > relied on internally. Imagine my embarrassment when I had to
> > explain on -user-fr the cause of the error occurring with
> > the code (minimized here):
> >
> > cons = \markup \tiny "conséquent"
> >
> > {
> >    \stemDown
> >    c'2^\cons
> >    \undo \stemDown
> >    c'2
> > }
> That code works fine here and produces the expected result:


Didn't check development versions. With 2.22.1, you get

Parsing.../home/jean/lilypond2.22.1/lilypond/usr/share/lilypond/current/ly/music-functions-init.ly:1962:18: 
In expression (cons (make-music # # ...) overrides):

/home/jean/lilypond2.22.1/lilypond/usr/share/lilypond/current/ly/music-functions-init.ly:1962:18: 
Wrong type to apply: (#<procedure tiny-markup (layout props arg)> 
"conséquent")


This seems a likely cause for current success:


commit b0c6d48388c66aa12a472a6069f5b2ec07c579b2
Author: Han-Wen Nienhuys <hanwenn@gmail.com>
Date:   Sun Feb 14 11:15:17 2021 +0100

    Initialize session from a dedicated parser

    The session mechanism reads the initialization .ly files, to setup
    variable assignments to replay for later files.  This mechanism
    inherently retains the module associated with the parser for
    initializing the session.

    Before, if the first .ly file assigned something to an identifier, 
the value
    would be retained, leading to "parsed-object is dead" warnings.

    By executing the initialization in a separate parser, we avoid the
    warnings. It also ensures that the first file is processed in the same
    way as later files.