Download of 2.23.7-9

Hello, When looking inside: http://lilypond.org/download/binaries/linux-64/ ...I see that 2.23.7,8,9 are not available for download. Why? Thanks! P

Error with -dbackend=null (Lilypond 2.23.10)

Hello, lilypond -dbackend=null foo.ly produces the following error: GNU LilyPond 2.23.10 (running Guile 2.2) Processing `foo.ly' Parsing... foo.ly:1: warning: no \version statement found, please add \version "2.23.10" for future compatibility Interpreting music... Preprocessing graphical objects.

Re: Error with -dbackend=null (Lilypond 2.23.10)

> Le 10 juil. 2022 à 12:43, Paolo Prete a écrit : > >  > Hello, > > lilypond -dbackend=null foo.ly produces the following error: > > GNU LilyPond 2.23.10 (running Guile 2.2) > Processing `foo.ly' > Parsing... > foo.ly:1: warning: no \version statement found, please add > \version "2.23.10" >

Re: Download of 2.23.7-9

> Le 10 juil. 2022 à 12:39, Paolo Prete a écrit : > >  > Hello, > > When looking inside: > > http://lilypond.org/download/binaries/linux-64/ > > ...I see that 2.23.7,8,9 are not available for download. Why? > > Thanks! That’s https://gitlab.com/lilypond/lilypond/-/issues/6371 You can fi

`ly:context-property` and empty alist

The documentation of `ly:context-property` is as follows. -- Function: ly:context-property context sym def Return the value for property SYM in CONTEXT. If DEF is given, and property value is ‘'()’, return DEF. I have a use case where I want to say ``` \set SYM = #'() ``` i.e., I

Re: `ly:context-property` and empty alist

> Le 10 juil. 2022 à 13:47, Werner LEMBERG a écrit : > >  > The documentation of `ly:context-property` is as follows. > > -- Function: ly:context-property context sym def > > Return the value for property SYM in CONTEXT. If DEF is given, > and property value is ‘'()’, return DEF.

Re: Error with -dbackend=null (Lilypond 2.23.10)

It Is very useful when I have to quickly correct syntax errors on a code that doesn't compile: given that It doesn't produce output, It shortens the time required for compiling. Is there an alternative that I can use? Thanks, Best P On Sunday, July 10, 2022, Jean Abou Samra wrote: > > > Le 10

Re: `ly:context-property` and empty alist

Hello Werner, the problem here is not really ly:context-property, but the C-implementation Context::internal_get_property, which uses SCM_EOL as default value. So Lilypond’s guile interface cannot know if a NULL is actually set or if the context property is not set. It would be possible to chec

Re: `ly:context-property` and empty alist,Re: `ly:context-property` and empty alist

> the problem here is not really ly:context-property, but the > C-implementation Context::internal_get_property, which uses SCM_EOL > as default value. [...] Thanks for the explanation! > #(define (context-has-defined? context sym) >(eq? (ly:context-property-where-defined context sym) conte

Re: `ly:context-property` and empty alist

>> I have a use case where I want to say >> >> ``` >> \set SYM = #'() >> ``` >> >> i.e., I explicitly want to override the default DEF with an empty >> list. How can I do that? > > As a user, if the code is written that way, you have no proper > solution. Yes, that’s a bit sad. (If the property

Re: Error with -dbackend=null (Lilypond 2.23.10)

Hello, Please keep the list posted. Le 10/07/2022 à 14:19, Paolo Prete a écrit : It Is very useful when I have to quickly correct syntax errors on a code that doesn't compile: given that It doesn't produce output, It shortens the time required for compiling. Is there an alternative that I can

Re: `ly:context-property` and empty alist

Le 10/07/2022 à 14:32, Valentin Petzel a écrit : Hello Werner, the problem here is not really ly:context-property, but the C-implementation Context::internal_get_property, which uses SCM_EOL as default value. So Lilypond’s guile interface cannot know if a NULL is actually set or if the contex

Re: Error with -dbackend=null (Lilypond 2.23.10)

I just used -dno-print-pages as an alternative, and it works. Will it be removed too in the future? thanks On Sun, Jul 10, 2022 at 5:30 PM Jean Abou Samra wrote: > Hello, > > Please keep the list posted. > > Le 10/07/2022 à 14:19, Paolo Prete a écrit : > > It Is very useful when I have to quick

Re: Error with -dbackend=null (Lilypond 2.23.10)

Le 10/07/2022 à 17:38, Paolo Prete a écrit : I just used -dno-print-pages as an alternative, and it works. Will it be removed too in the future? I can't speak for future developers of LilyPond. On the other hand, unlike -dbackend=null, -dno-print-pages is documented with an explanation of its

Re: Error with -dbackend=null (Lilypond 2.23.10)

Jean Abou Samra writes: > Le 10/07/2022 à 17:38, Paolo Prete a écrit : >> I just used -dno-print-pages as an alternative, and it works. >> Will it be removed too in the future? > > > I can't speak for future developers of LilyPond. On > the other hand, unlike -dbackend=null, -dno-print-pages > is

Mark formatter changed in v2.23?

Hi all, I was super excited to see the new D.S. and D.C. support coming in the next release (I have several scores where I've had to fake this) so decided to take a chance and upgrade to the devel release. Mostly everything works fine, but I discovered that the command I typically use to set the

Re: Error with -dbackend=null (Lilypond 2.23.10)

? On Sunday, July 10, 2022, David Kastrup wrote: > Jean Abou Samra writes: > > > Le 10/07/2022 à 17:38, Paolo Prete a écrit : > >> I just used -dno-print-pages as an alternative, and it works. > >> Will it be removed too in the future? > > > > > > I can't speak for future developers of LilyPond

Re: Error with -dbackend=null (Lilypond 2.23.10)

Paolo Prete writes: >> On Sunday, July 10, 2022, David Kastrup wrote: >> >>> Jean Abou Samra writes: >>> >>> > Le 10/07/2022 à 17:38, Paolo Prete a écrit : >>> >> I just used -dno-print-pages as an alternative, and it works. >>> >> Will it be removed too in the future? >>> > >>> > >>> > I can't

Re: Mark formatter changed in v2.23?

Le 10/07/2022 à 22:55, Benjamin Tordoff a écrit : Hi all, I was super excited to see the new D.S. and D.C. support coming in the next release (I have several scores where I've had to fake this) so decided to take a chance and upgrade to the devel release. Mostly everything works fine, but I

Re: Mark formatter changed in v2.23?

Thanks for the rapid response - I’ll run the update. I’ve never tried Frescobaldi, but maybe I should! (I’ve been using lilypond from the command line for 20+ years and for hundreds of scores and parts so old habits are hard to break!) Thanks for all the work you and others put into this essent

Re: Mark formatter changed in v2.23?

Le 10/07/2022 à 23:14, Benjamin Tordoff a écrit : Thanks for the rapid response - I’ll run the update. I’ve never tried Frescobaldi, but maybe I should! (I’ve been using lilypond from the command line for 20+ years and for hundreds of scores and parts so old habits are hard to break!) I w

Re: Error with -dbackend=null (Lilypond 2.23.10)

On Sun 10 Jul 2022 at 23:08:19 (+0200), David Kastrup wrote: > Paolo Prete writes: > >> On Sunday, July 10, 2022, David Kastrup wrote: > >>> Jean Abou Samra writes: > >>> > Le 10/07/2022 à 17:38, Paolo Prete a écrit : > >>> >> I just used -dno-print-pages as an alternative, and it works. > >>> >

Re: Mark formatter changed in v2.23?

> On Jul 10, 2022, at 3:55 PM, Benjamin Tordoff wrote: > > { > \set Score.markFormatter = #format-mark-box-alphabet > R1 > \mark \default % Should be boxed but isn't > R1 > } > The “new” command is \set Score.rehearsalMarkFormatter = #format-mark-box-letters (See