Re: How to submit a feature request (issue)

[Curt McDowell]

I tend not to use convert-ly because I feel upgrading a file version 
would unfairly force anyone who wants to compile my music to upgrade 
their LilyPond installation. Upgrading might not be straightforward when 
using a standard distro, and I'd hate for someone to risk destabilizing 
their working environment on my account. Using convert-ly would only 
serve as a barrier to compiling my files, most of which are still on 
2.18 and compile with 2.22 (I can't think of a case where something broke).

Regards,
Curt

On 6/30/2023 3:36 PM, Stu McKenzie wrote:
> I'm not sure how to submit a feature request issue.
>
> I'd like to request the following change to the LilyPond parser:
>
> One feature that would be useful is for the LilyPond parser to output 
> the following version numbers:
> The LilyPond version, e.g. 2.24.1;
> The source file "\version", e.g. 2.22.0.
>
> If one changes the version number to a number greater than the current 
> version, the output is:
> Parsing...
> error: program too old: 2.24.1 (file requires: 2.25.0)
>
> This shows that the parser is checking the versions, so to output the 
> version numbers shouldn't require much additional coding.
>
> If the versions are always output, this would serve as confirmation 
> that a source file is up to date, and also remind users if convert-ly 
> has, or hasn't, been performed on a source file.
>
> Perhaps this could be extended to check versions of any files included 
> by the source file (this may be a bit too complicated!).
>
> Would those more familiar with bug and issue reporting guide me as to 
> whether or not this is worth pursuing, and if so, how to proceed?