Michael, I'm sorry, but I don't really understand what your code does, nor do I know what to do with it in a real score. If you want to throw a score at me using it I'll be happy to run LilyPond 2.25.17 (Guile 3.0) and let you know the results.
-David > From: "Michael Käppler" <[email protected]> > To: "bobroff" <[email protected]>, "Jean Abou Samra" <[email protected]> > Cc: "Lillypond Users Mailing List" <[email protected]> > Sent: Thursday, June 27, 2024 8:31:12 PM > Subject: Re: Windows users - Call for testing > Thanks, but could you give it a try on a real score? That would be very > helpful! > Michael > Am 27.06.2024 um 15:30 schrieb [ mailto:[email protected] | > [email protected] > ] : >> Tried again with the code 'massaged' by Jean. Here's the output: >> $ ./bin/lilypond.exe test.ly >> GNU LilyPond 2.25.17 (running Guile 3.0) >> Processing `test.ly' >> Parsing...1/2 >> -7/2 >> #f >> Success: compilation successfully completed >>> From: "Jean Abou Samra" [ mailto:[email protected] | <[email protected]> ] >>> To: "Michael Käppler" [ mailto:[email protected] | <[email protected]> ] , >>> "bobroff" [ mailto:[email protected] | <[email protected]> ] >>> Cc: "Lillypond Users Mailing List" [ mailto:[email protected] | >>> <[email protected]> ] >>> Sent: Thursday, June 27, 2024 1:24:14 PM >>> Subject: Re: Windows users - Call for testing >>> > Hmm, but that looks like syntax errors in your test.ly file that are >>> > unrelated >>> > to the Guile patches. >>> As can be seen in the list archives, Klaus' mail client inserted spurious >>> newlines >>> that turn parts of comments into non-comments. The correct code should be >>> #(define step 1) >>> #(define cnt -3) >>> #(define limit (+ cnt 0.3)) >>> #(display (/ step 2)) >>> #(newline) >>> #(display (- cnt (/ step 2))) >>> #(newline) >>> #(display (> (- cnt (/ step 2)) limit))
