5 ms·

Handling command-line arguments in Bash is easy. Bash's `getopts` handles short and long arguments gnu-style without any problem, out of the box, without any ne

Handling command-line arguments in Bash is easy. Bash's `getopts` handles short and long arguments gnu-style without any problem, out of the box, without any need for libraries or complicated packages. This pattern handles lots of styles of options: short and long options (-h, --help), `--` for separating options from positional args, with GNU-style long options (--output-file=$filename). while getopts :o:h-: option do case $option in h ) print_help;; o ) output_file=$OPTARG;; - ) case $OPTARG in help ) print_help;; output-file=* ) output_file=${OPTARG##*=};; * ) echo "bad option $OPTARG" >&2; exit 1;; esac;; '?' ) echo "unknown option: $OPTARG" >&2; exit 1;; : ) echo "option missing argument: $OPTARG" >&2; exit 1;; * ) echo "bad state in getopts" >&2; exit 1;; esac done shift $((OPTIND-1)) (( $# > 0 )) && printf 'remaining arg: %s\n' "$@"

sacnoradhq 4y ago
I don't know where you learned shell scripting, but your formatting is very confusing and nonstandard. - while...; do / if ...; then - space before ;; - no space before case match - use util-linux getopt because getopts doesn't handle long args - DRY with a die() function rather than exits littered all over
- fsckboy 4y ago
  >I don't know where you learned shell scripting, but your formatting is very confusing i don't know where you learned English composition, but I can't follow your critique. are you pointing out your preferences (which may well match gnu or bsd standards, i don't know tell me) or things that actually make a difference? Did he break emacs auto-indent? Are you pointing out all the flaws or the correct ways, i'm having to eyeball diff. Use more of your words. while do doesn't seem substantially worse/confusing compared to while;do unless you have some reason? spacing out ;; does it make a difference? or do you like things spaced out? etc.
  - sacnoradhq 4y ago
    Flagged for not being a professional response to constructive feedback.
    - yesenadam 4y ago
      I thought it was "professional", helpful, and a great comment. I didn't think yours was constructive, just unhelpfully treating a different formatting style as objectively worse, in an unfriendly way. "Be kind"! It was also hard to parse, as the GP pointed out. edit: You changed your comment after I wrote this. Now it mentions that you flagged the GP. That's ridiculous.
      - sacnoradhq 4y ago
        You have way too much time on your hands and seem determined to argue nonconstructively. Have a good one.
        yesenadam 4y ago
        > You have way too much time on your hands and seem determined to argue nonconstructively. Have a good one. Please refresh on the HN comment guidelines. And reconsider who has been "constructive" vs "nonconstructive" in this thread.
- databasher 4y ago
  If you refer to my example above, you'll find that Bash's native "getopts" handles long options just fine. It accepts short option `-`, with an argument. This handles --long-options and --long-options=with-arguments. Feel free to use your own formatting preferences.
  - sacnoradhq 4y ago
    https://google.github.io/styleguide/shellguide.html https://google.github.io/styleguide/shellguide.html
JoBrad 4y ago
The video in the linked page mentions this.
- databasher 4y ago
  The video in the linked page says that getopts only supports short options.

sacnoradhq 4y ago

I don't know where you learned shell scripting, but your formatting is very confusing and nonstandard. - while...; do / if ...; then - space before ;; - no space before case match - use util-linux getopt because getopts doesn't handle long args - DRY with a die() function rather than exits littered all over

fsckboy 4y ago
>I don't know where you learned shell scripting, but your formatting is very confusing i don't know where you learned English composition, but I can't follow your critique. are you pointing out your preferences (which may well match gnu or bsd standards, i don't know tell me) or things that actually make a difference? Did he break emacs auto-indent? Are you pointing out all the flaws or the correct ways, i'm having to eyeball diff. Use more of your words. while do doesn't seem substantially worse/confusing compared to while;do unless you have some reason? spacing out ;; does it make a difference? or do you like things spaced out? etc.
- sacnoradhq 4y ago
  Flagged for not being a professional response to constructive feedback.
  - yesenadam 4y ago
    I thought it was "professional", helpful, and a great comment. I didn't think yours was constructive, just unhelpfully treating a different formatting style as objectively worse, in an unfriendly way. "Be kind"! It was also hard to parse, as the GP pointed out. edit: You changed your comment after I wrote this. Now it mentions that you flagged the GP. That's ridiculous.
    - sacnoradhq 4y ago
      You have way too much time on your hands and seem determined to argue nonconstructively. Have a good one.
      - yesenadam 4y ago
        > You have way too much time on your hands and seem determined to argue nonconstructively. Have a good one. Please refresh on the HN comment guidelines. And reconsider who has been "constructive" vs "nonconstructive" in this thread.
databasher 4y ago
If you refer to my example above, you'll find that Bash's native "getopts" handles long options just fine. It accepts short option `-`, with an argument. This handles --long-options and --long-options=with-arguments. Feel free to use your own formatting preferences.
- sacnoradhq 4y ago
  https://google.github.io/styleguide/shellguide.html https://google.github.io/styleguide/shellguide.html

JoBrad 4y ago

The video in the linked page mentions this.

databasher 4y ago
The video in the linked page says that getopts only supports short options.