Now how did I miss that? Face-palm :-)
Thanks,
Ken
On Wed, Mar 1, 2023 at 11:40 PM Mark Knoop wrote:
>
>
> At 17:41 on 01 Mar 2023, Kenneth Wolcott wrote:
> > Hi;
>
> > I think that convert-ly should write the current version to the
> > converted file(s).
>
> > If that statement is correct,
At 17:41 on 01 Mar 2023, Kenneth Wolcott wrote:
> Hi;
> I think that convert-ly should write the current version to the
> converted file(s).
> If that statement is correct, then Lilypond version 2.24.1 writes the
> older version (2.24.0) to the converted file(s).
Please see the -c,
Thanks, Jean.
That makes sense.
But the implication is it should based on the fact that the conversion
history shows all the minor versions along the way...
Thanks,
Ken
On Wed, Mar 1, 2023 at 6:05 PM Jean Abou Samra wrote:
>
> Le mercredi 01 mars 2023 à 17:41 -0800, Kenneth Wolcott a écrit :
Le mercredi 01 mars 2023 à 17:41 -0800, Kenneth Wolcott a écrit :
> Hi;
>
> I think that convert-ly should write the current version to the
> converted file(s).
>
> If that statement is correct, then Lilypond version 2.24.1 writes the
> older version (2.24.0) to the converted file(s).
I
Hi;
I think that convert-ly should write the current version to the
converted file(s).
If that statement is correct, then Lilypond version 2.24.1 writes the
older version (2.24.0) to the converted file(s).
Here's my test script invocation:
./test_conversion_version.bash | tee
