Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example file doesn't work (bad destination `~a' "~A.~A") #30

Open
kwertyops opened this issue Jan 29, 2023 · 4 comments
Open

Example file doesn't work (bad destination `~a' "~A.~A") #30

kwertyops opened this issue Jan 29, 2023 · 4 comments

Comments

@kwertyops
Copy link

Using the example lilypond file from the README, and the following command:

lilypond -I ~/Code/openlilylib -V testlyexport.ly

Results in the following:

<snipped>
...
...
In unknown file:
           4 (ly:parse-string-expression #<Lily_parser #<Lily_lexer…> …)
In /private/tmp/lilypond-20230104-5751-ij2w8a/lilypond-2.24.0/out/share/lilypond/current/scm/lily/ly-syntax-constructors.scm:
    47:22  3 (music-function #<Music function #<procedure 107f8d4c0…> …)
In ice-9/eval.scm:
   293:34  2 (_ #(#(#(#(#<directory (lilypond-export api) …>) …) …) …))
   173:55  1 (_ #(#(#(#(#<directory (lilypond-export api) …>) …) …) …))
In ice-9/format.scm:
     52:8  0 (format "~A.~A" "testlyexport" "krn")

ice-9/format.scm:52:8: In procedure format:
format: bad destination `~a' "~A.~A"
@jeanas
Copy link
Member

jeanas commented Jan 30, 2023

This repo is not compatible with LilyPond 2.24.

@PaulMorris
Copy link

This looks like the following issue (from http://lilypond.org/doc/v2.24/Documentation/changes/index.html):

"The format function now requires a boolean or port as the first argument. This argument was optional in Guile 1.8. In order to make the function return the formatted output as a string, like format does without this argument in Guile 1.8, pass #f for this argument, i.e., (format #f "string" arguments …) instead of (format "string" arguments …)."

@jeanas
Copy link
Member

jeanas commented Jan 31, 2023

Yup. But it may only be the surface of problems.

@jeanas
Copy link
Member

jeanas commented Jan 31, 2023

E.g. #29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants