Le lundi 03 avril 2023 à 21:32 +0200, David Kastrup a écrit :
>
> dak@lola:/usr/local/tmp/lilypond$ lilypond scheme-sandbox
> GNU LilyPond 2.25.0 (running Guile 2.2)
> Processing `/usr/local/share/lilypond/2.25.0/ly/scheme-sandbox.ly'
> Parsing...
> GNU Guile 2.2.7
> Copyright (C) 1995-2019 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(#{ g217}#)> #{ - #}
>
> <string>:1:3: error: syntax error, unexpected end of input, expecting \etc
> -
>
> /usr/local/share/lilypond/2.25.0/ly/scheme-sandbox.ly:34:2: error: error in
> #{ ... #}
> #
> (cond-expand
> scheme@(#{ g217}#)>
>
>
> Note: compilation failed and \version outdated, did you
> update input syntax with convert-ly?
>
>
> [https://lilypond.org/doc/v2.25/Documentation/usage/updating-files-with-convert_002dly](https://lilypond.org/doc/v2.25/Documentation/usage/updating-files-with-convert_002dly)
>
> fatal error: failed files: "scheme-sandbox"Well, “Success: compilation successfully completed” at the end of a scheme-sandbox run does not make a whole lot of sense either. Perhaps we should reimplement "lilypond scheme-sandbox" in a way that does not use a scheme-sandbox.ly file.
signature.asc
Description: This is a digitally signed message part
