mirror of
https://github.com/clap-rs/clap
synced 2024-12-14 14:52:33 +00:00
83d6add9aa
In surveying various tools and CLI parsers, I noticed they list the subcommands first. This puts an emphasis on them which makes sense because that is most likely what an end user is supposed to pass in next. Listing them last aligns with the usage order but it probably doesn't outweigh the value of getting a user moving forward.
783 B
783 B
$ 01_quick --help
clap [..]
A simple to use, efficient, and full-featured Command Line Argument Parser
Usage:
01_quick[EXE] [OPTIONS] [name] [SUBCOMMAND]
Subcommands:
test does testing things
help Print this message or the help of the given subcommand(s)
Arguments:
<name> Optional name to operate on
Options:
-c, --config <FILE> Sets a custom config file
-d, --debug... Turn debugging information on
-h, --help Print help information
-V, --version Print version information
By default, the program does nothing:
$ 01_quick
Debug mode is off
But you can mix and match the various features
$ 01_quick -dd test
Debug mode is on
Not printing testing lists...