openlilylib / lilypond-export

LilyPond export API to write Humdrum, MusicXML and more
GNU General Public License v3.0
22 stars 8 forks source link

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

Open kwertyops opened 1 year ago

kwertyops commented 1 year ago

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 commented 1 year ago

This repo is not compatible with LilyPond 2.24.

PaulMorris commented 1 year ago

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 commented 1 year ago

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

jeanas commented 1 year ago

E.g. #29