Re: debug scheme part working with Frescobaldi

Eef Weenink wrote: I have several lines of scheme, somewhere is probably an syntax error. The only message I get is form lilypond log: there is an error in the line # begin etcetera. (that is the first line of the scheme segment). I want to zoom in, and see what specific problem there is,

Re: debug scheme part working with Frescobaldi

I don't know if this is helpful but debug print statements, the last resort of the desperate, are sometimes useful. % simple debug print #(define (dbg . args)    "Simple debug console print."    (cond     ((not (null? args)) (display (car args)) (display " ") (apply dbg (cdr

Re: debug scheme part working with Frescobaldi

Le 20/07/2022 à 08:22, Eef Weenink a écrit : I use 2.22 and arranger.ly  (from Giles Thibault) My question is more general. (and maybe mostly related to Frescobaldi as an enviroment). I have several lines of scheme, somewhere is probably an syntax error. The only

Re: debug scheme part working with Frescobaldi

I use 2.22 and arranger.ly (from Giles Thibault) My question is more general. (and maybe mostly related to Frescobaldi as an enviroment). I have several lines of scheme, somewhere is probably an syntax error. The only message I get is form lilypond log: there is an error in

Re: debug scheme part working with Frescobaldi

Am Di., 19. Juli 2022 um 21:40 Uhr schrieb Eef Weenink : > > So I am start working with scheme parts in my liypond files (using > arranger.ly). Using Frescobalid to input all > When compiling I keep getting messages: > > GUILE signaleerde een fout voor de hier beginnende expressie > > It would be

debug scheme part working with Frescobaldi

So I am start working with scheme parts in my liypond files (using arranger.ly). Using Frescobalid to input all When compiling I keep getting messages: GUILE signaleerde een fout voor de hier beginnende expressie It would be nice to know what error I made. I read I should