You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, it would be nice if gregorio, when invoked with no arguments, just said something like:
gregorio: missing file operand
Try 'gregorio --help' for more information.
instead of dumping the whole usage message.
Similarly, when there is an error in arg parsing, an invocation like "gregorio -o" with no argument, it's nicer to just report the error and give the suggestion instead of dumping the whole usage message. That is usually too much info.
Also, the spaces before colons ("Usage :", "is :"), while I know are usual in French, are just weirdly wrong in English. There's also no need for the newline before "Usage", or the newline after the "Usage:", or an extra newline at the end. Fewer lines is better.
Also, it is highly useful to write a sentence or two about what the program does in the --help message. Something like "Engrave Gregorian chant scores: convert a gabc file to GregorioTeX."
Also, it's typical to capitalize metavariables like "FORMAT" and "FILE" in the help message.
Also, the help message could/should end with a url to the overall project home page.
Also, it is not usual to capitalize "Chant" in "Gregorian chant", as far as I've seen.
See pretty much any GNU --help (and --version) message for examples of all this in action. "mv --help" is reasonably short and instructive.
Happy helping.
The text was updated successfully, but these errors were encountered:
…miktex
* commit '1344625ef8f6222f67ac1b3068e91153531cc83e': (23 commits)
more messages to stderr, add message for non-fatal error cases
print usage in print_short_usage
document
fix doc pdf file names
improve code (no output change)
oops
address more comments
fix @henryso's notes, more coherent case
first attempt to fixgregorio-project#891
Rewording for clarity
Update Version number for new beta
final optimization (no test change)
Restored the #define for va_start/va_arg/va_end.
Eliminated problems found by clang static analysis. For gregorio-project#697.
document
withmora -> morawidth
more TeX perf optimizations
TeX performance optimization
first working attempt (doesn't work on different syllables)
Applied attributes to support functions.
...
it would be nice if gregorio supported the widespread --version option along with --help. Here is some info for it:
https://www.gnu.org/prep/standards/html_node/_002d_002dversion.html
Also, it would be nice if gregorio, when invoked with no arguments, just said something like:
gregorio: missing file operand
Try 'gregorio --help' for more information.
instead of dumping the whole usage message.
Similarly, when there is an error in arg parsing, an invocation like "gregorio -o" with no argument, it's nicer to just report the error and give the suggestion instead of dumping the whole usage message. That is usually too much info.
Also, the spaces before colons ("Usage :", "is :"), while I know are usual in French, are just weirdly wrong in English. There's also no need for the newline before "Usage", or the newline after the "Usage:", or an extra newline at the end. Fewer lines is better.
Also, it is highly useful to write a sentence or two about what the program does in the --help message. Something like "Engrave Gregorian chant scores: convert a gabc file to GregorioTeX."
Also, it's typical to capitalize metavariables like "FORMAT" and "FILE" in the help message.
Also, the help message could/should end with a url to the overall project home page.
Also, it is not usual to capitalize "Chant" in "Gregorian chant", as far as I've seen.
See pretty much any GNU --help (and --version) message for examples of all this in action. "mv --help" is reasonably short and instructive.
Happy helping.
The text was updated successfully, but these errors were encountered: