lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

How to submit a feature request (issue)


From: Stu McKenzie
Subject: How to submit a feature request (issue)
Date: Fri, 30 Jun 2023 15:36:40 -0700
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1


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?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]