c6222d42f8
There are quite some problems with the way commands are explained:
* Interactivity - command arguments gets explained as if one is
following a guide ("insert this, enter that"). Better explain them
without any "guidance"; use present tense to describe commands.
* Duplicity - the purpose of the command is explained over and over
when arguments are being described.
* Separation - there is no need to divide required and optional
command arguments into their respective sections. Their amount did
not grow up that much for this to make sense.
* mute_command_help.html: i64 would be sufficient for developers, but
not end users. It does not stop anyone from specifying overflowing
integer, after all.
|
||
|---|---|---|
| src | ||
| .gitignore | ||
| Cargo.toml | ||