Re: OLL not working with lilypond 2.22

[Jonas Hahnfeld]

Am Sonntag, dem 24.01.2021 um 12:01 +0100 schrieb Valentin Petzel:
> Ah, okay. Sitting on Deb Sid I didn’t notice.
> 
> Anyway, of course your check is much better, but mine does not depend on the 
> lilypond version, but on the guile version. It basically takes the first 
> number in the version string a.b.c and checks if a < 2.

Oh right, I missed that. Thanks for clarifying!

Jonas

> 
> Regards,
> Valentin
> 
> Am Sonntag, 24. Jänner 2021, 10:47:24 CET schrieb Jonas Hahnfeld:
> > Am Sonntag, dem 24.01.2021 um 00:54 +0100 schrieb Valentin Petzel:
> > > Hello,
> > > 
> > > Lilypond transitioned to guile 2.
> > 
> > No, it didn't. The default and only supported version right now is
> > Guile 1.8 and that's what is shipped in the official binary releases.
> > If your distribution provides you with LilyPond compiled against Guile
> > 2.2, file a bug with them (I know that at least Fedora 33 and Debian
> > sid do at the time of writing).
> > 
> > > Thus in core/internal/control.scm
> > > 
> > > (use-syntax (ice-9 syncase))
> > > 
> > > Will not be nescessary anymore and won’t work. We can replace it by
> > > 
> > > (if (< (string->number (car (string-split (version) #\.))) 2) (use-syntax
> > > (ice-9 syncase)))
> > 
> > An easier solution should be (cond-expand (guile-2 #f) (else ...))
> > which doesn't rely on the version of LilyPond.
> > 
> > Jonas
> > 
> > > which keeps compatibility to older Lilypond versions. In bezier/_internal/
> > > special-cpts-display.ily the statements
> > > 
> > > #(cond ((not (defined? 'debug-control-points-line-thickness))
> > >          0.05)))
> > > 
> > > &c. do not work anymore, one could fix this by doing
> > > 
> > > #(define debug-control-points-line-thickness
> > >    (if (not (defined? 'debug-control-points-line-thickness))
> > >          0.05
> > >          debug-control-points-line-thickness))
> > > 
> > > Regards,
> > > Valentin

signature.asc
Description: This is a digitally signed message part