Re: rehearsalMarkFormatter => markFormatter in 2.24.0

2023-03-12 Thread Richard Shann
On Sat, 2023-03-11 at 19:03 +0100, Jean Abou Samra wrote: > Le vendredi 10 mars 2023 à 14:35 +, Richard Shann a écrit : > > sorry, yes, I just assumed it had been shortened not lengthened. > It was renamed because LilyPond gained other “mark formatters”, such > as segnoMarkFormatter and

Re: rehearsalMarkFormatter => markFormatter in 2.24.0

2023-03-11 Thread Jean Abou Samra
Le vendredi 10 mars 2023 à 14:35 +, Richard Shann a écrit : > sorry, yes, I just assumed it had been shortened not lengthened. It was renamed because LilyPond gained other “mark formatters”, such as segnoMarkFormatter and codaMarkFormatter. > for anyone listening in that needs an extra ")"

Re: rehearsalMarkFormatter => markFormatter in 2.24.0

2023-03-10 Thread Richard Shann
On Fri, 2023-03-10 at 14:12 +0100, Jean Abou Samra wrote: > > > > Le 10 mars 2023 à 13:47, Richard Shann a > > écrit : > > > > I've noticed a name change in 2.24 where > > rehearsalMarkFormatter has become markFormatter. > > > (You mean the other way around.) sorry, yes, I just assumed it

Re: rehearsalMarkFormatter => markFormatter in 2.24.0

2023-03-10 Thread Jean Abou Samra
> Le 10 mars 2023 à 13:47, Richard Shann a écrit : > > I've noticed a name change in 2.24 where > rehearsalMarkFormatter has become markFormatter. (You mean the other way around.) > I want to make scores that can be compiled under either 2.22 or 2.24 so > I tried this: > >

rehearsalMarkFormatter => markFormatter in 2.24.0

2023-03-10 Thread Richard Shann
I've noticed a name change in 2.24 where rehearsalMarkFormatter has become markFormatter. I want to make scores that can be compiled under either 2.22 or 2.24 so I tried this: 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< \version "2.24.0" xxx = rehearsalMarkFormatter