3 ms·
With this thread, wondering what specs/guidelines (if any) are there for common option behavior? For example, -v, —-version -o <file>, —-output=<file> if <
by kickingvegas 4y ago
With this thread, wondering what specs/guidelines (if any) are there for common option behavior?
For example,
-v, —-version
-o <file>, —-output=<file> if <file> is - then use stdout
-i <file>, —-input=<file>. if <file> is - then use stdin
-h, —-help
Or is it just anarchy out here?
- conaclos 4y ago-v is also used for --verbose. In this case -V is often used for --version. Another common option I am thinking about is -r for --recursive. I could advocate to use only commonly accepted short options.
- conaclos 4y agoI found guidelines [1] that list several common short options: -a, --all -d, --debug -f, --force -h, --help -o, --output -p, --port -q, --quiet -u, --user [1] https://clig.dev/#arguments-and-flags https://clig.dev/#arguments-and-flags