The Gnu-ish convention of -abcd --word command flags using one vs two dashes to distinguish combining short flags from non-combined word-ish flags is inherently prone to this.
Most arg parsing libs are poor at warning/detecting this. $ ls -escape ls: invalid option -- 'e' Try 'ls --help' for more information. OTOH, 'git' does: $ git status -short error: did you mean `--short` (with two dashes ?) A proper fix to this -- to emulate git -short's helpful message -- would require giving Getopt::Long a PullRequest (or a Fork). This becomes second nature after a decade of Gnu exposure; even us pre-SystemIII graybeards are adapting, but it may be extra confusing to WIN/OSX users who aren't XTERM CMD-os. This apples to -cc -css -csv -go -hh -rr Most erroneous single-dash -word mis-uses will error sensibly, but only because we don't have all single letters in use: $ ack -perl Unknown option: p Unknown option: e ack: Invalid option on command line (If the -type contains deprecated flags a, or u, the long ack1 vs ack2 error message is however extra confusing. ) i would agree with Sato's comment that "ack --help-types" is a good place to warn about this, probably in main POD args section too. -- You received this message because you are subscribed to the Google Groups "ack users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/ack-users. For more options, visit https://groups.google.com/d/optout.
