Here's the output: -------- GNU LilyPond 2.23.6 (running Guile 1.8) command line options: "((backend . eps test.ly) (gs-api . #f) )"<unnamed port>: In procedure scm_i_lreadparen in expression (dynamic-wind swaports thunk ...): <unnamed port>: #<unknown port>:1:18: in pair: missing close paren --------
I'm using the latest git master (just updated this morning). Running on Linux (debian/testing), not compiling with Cairo. Should I rollback git to the latest release to see if it makes a difference? --T On Mon, Dec 13, 2021 at 10:37:17PM +0100, Jean Abou Samra wrote: > Le 13/12/2021 à 20:54, Jean Abou Samra a écrit : > > #(display (ly:command-line-code)) > > > Silly me. It should print nothing at all since the error is > occurring before LilyPond even starts parsing the file. > Rather, try to change scm/lily.scm by applying the attached > patch (`git apply show-command-line-code.patch`). > > Thanks, > Jean > > > diff --git a/scm/lily.scm b/scm/lily.scm > index c5c905b3ca..89563d9e2c 100644 > --- a/scm/lily.scm > +++ b/scm/lily.scm > @@ -436,6 +436,8 @@ messages into errors.") > (ly:set-option 'debug-gc-object-lifetimes #f)) > (else)) > > +(ly:message "command line options: ~s" (ly:command-line-options)) > + > (for-each (lambda (x) > (ly:set-option (car x) (cdr x))) > (with-input-from-string (ly:command-line-options) read)) > @@ -846,6 +848,7 @@ PIDs or the number of the process." > > (define-public (lilypond-main files) > "Entry point for LilyPond." > + (ly:message "command line code: ~s" (ly:command-line-code)) > (eval-string (ly:command-line-code)) > (if (ly:get-option 'help) > (begin (ly:option-usage) -- Freedom: (n.) Man's self-given right to be enslaved by his own depravity.