Le 25/03/2022 à 15:28, Lukas-Fabian Moser a écrit :
I don't see one either, but there appear to be scores in the wild that
use them (I saw an example on the user list, which is what triggered
the original post). The question is whether we consider it fine to
start giving an error on them (it
I don't see one either, but there appear to be scores in the wild that
use them (I saw an example on the user list, which is what triggered
the original post). The question is whether we consider it fine to
start giving an error on them (it's not a fatal error, doesn't prevent
compilation of th
Le 25/03/2022 à 13:05, Michael Käppler a écrit :
Am 22.03.2022 um 12:57 schrieb Jean Abou Samra:
Hi,
With https://gitlab.com/lilypond/lilypond/-/merge_requests/1187,
I introduced a change that I didn't notice: something like
\version "2.23"
is now an error. It is accepted with current release
Am 22.03.2022 um 12:57 schrieb Jean Abou Samra:
Hi,
With https://gitlab.com/lilypond/lilypond/-/merge_requests/1187,
I introduced a change that I didn't notice: something like
\version "2.23"
is now an error. It is accepted with current released versions.
On the other hand, convert-ly has alwa
On Mar 22, 2022, at 07:57, Jean Abou Samra wrote:
>
> Hi,
>
> With https://gitlab.com/lilypond/lilypond/-/merge_requests/1187,
> I introduced a change that I didn't notice: something like
>
> \version "2.23"
>
> is now an error. It is accepted with current released versions.
> On the other han
Hi,
With https://gitlab.com/lilypond/lilypond/-/merge_requests/1187,
I introduced a change that I didn't notice: something like
\version "2.23"
is now an error. It is accepted with current released versions.
On the other hand, convert-ly has always rejected such version
strings. Should we accep
