27 ms·

The install page says that `sudo configure.sh -install` is the install command. The command is actually `sudo ./configure.sh -install`. Further, it should proba

by 333c 9y ago

The install page says that `sudo configure.sh -install` is the install command. The command is actually `sudo ./configure.sh -install`. Further, it should probably be `sudo ./configure.sh --install` (with two hyphens), as is convention for named (edit: long-form) options on the command line.

craftyguy 9y ago
> as is convention for named options on the command line. Gosh, I really wish that people would follow a convention for named options on the command line. I don't even really care which one, as long as they were all consistent in picking one.
- reaperducer 9y ago
  I've seen /, -, --, and +. Any other ones leap to mind? I wonder if there's a complete list somewhere.
  - pash 9y ago
    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_002dLine-Interfaces.html https://www.gnu.org/prep/standards/html_node/Command_002dLin... 1. http://www.catb.org/esr/writings/taoup/html/ch10s05.html http://www.catb.org/esr/writings/taoup/html/ch10s05.html
    - 333c 9y ago
      Thanks, this is what I meant in my original comment. I said "named" when I really meant "long-form," as you said.
    - JetSpiegel 9y ago
      > python -v That's verbose mode, not Version. You want a capitalized V.
  - zerokernel 9y ago
    option=value, option:value, option/value and even option\value (without dashes). Not joking.

by 333c 9y ago

craftyguy 9y ago

> as is convention for named options on the command line. Gosh, I really wish that people would follow a convention for named options on the command line. I don't even really care which one, as long as they were all consistent in picking one.

reaperducer 9y ago
I've seen /, -, --, and +. Any other ones leap to mind? I wonder if there's a complete list somewhere.
- pash 9y ago
  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_002dLine-Interfaces.html https://www.gnu.org/prep/standards/html_node/Command_002dLin... 1. http://www.catb.org/esr/writings/taoup/html/ch10s05.html http://www.catb.org/esr/writings/taoup/html/ch10s05.html
  - 333c 9y ago
    Thanks, this is what I meant in my original comment. I said "named" when I really meant "long-form," as you said.
  - JetSpiegel 9y ago
    > python -v That's verbose mode, not Version. You want a capitalized V.
- zerokernel 9y ago
  option=value, option:value, option/value and even option\value (without dashes). Not joking.