Re:LuLu: An open-source macOS firewall that blocks unknown o...
by pash on Friday January 19, 2018 @02:57PM
(#16189228)
The usual convention is a single hyphen for short-form (single-letter) options, and a double hyphen for long-form options:
> python -v
or > python —-version
It’s good practice to offer both. It should also be possible to set multiple options at once by appending one after another in short form following a single hyphen: > ls -alR
is the same as > ls -a -l -R
Long-form options are technically a GNU thing [0] and are not mentioned in the POSIX standard, but they’re conventional enough now that I think it’s good practice to include them in any CLI program.There are also a number of looser conventions about the meaning of certain short-form options [1].
0. https://www.gnu.org/prep/standards/html_node/Command_002dLin...
Re:LuLu: An open-source macOS firewall that blocks unknown o...
by 333c on Friday January 19, 2018 @03:09PM
(#16189336)
Thanks, this is what I meant in my original comment. I said "named" when I really meant "long-form," as you said.
Re:LuLu: An open-source macOS firewall that blocks unknown o...
by JetSpiegel on Saturday January 20, 2018 @05:18AM
(#16192848)
> python -v
That's verbose mode, not Version. You want a capitalized V.
Re:LuLu: An open-source macOS firewall that blocks unknown o...
by zerokernel on Friday January 19, 2018 @05:28PM
(#16190467)
option=value, option:value, option/value and even option\value (without dashes). Not joking.
I wonder if there's a complete list somewhere.