3 ms·
The worst is a few tools where when you type: the_command -foo ...and the tool responds with: -foo: No such option. You probably meant --foo Well sh
by ryandrake 3y ago
The worst is a few tools where when you type:
the_command -foo
...and the tool responds with:
-foo: No such option. You probably meant --foo
Well shit! Thank you for that burst of empathy. If you, developer, are that confident that's what I meant why couldn't you just make both inputs do the same thing? You went out of your way to make the code handle -foo, but only to have the program fire off that snide remark instead of doing what you know the user meant to do. Maddening.
- Ntrails 3y agoGiven the number of times I run git psuh To be told "you probably mean push"... yeah it'd be easier for me if they went ahead and accepted the typo :D
- Joker_vD 3y agoJust add [alias] psuh = push to your ~/.gitconfig? I personally have "ull = pull" and "ush = push" in this section, together with "alias gitp='git'" in my ~/.bash_aliases because of how often I type "gitp ull".
- Ntrails 3y agoI have "st = status" but you're absolutely right I should probably get around to updating!
- rrobukef 3y agoBecause you may have meant --f=oo or -f -o -o, both of which are standard unix interpretations of single-dash multi-character flags (e.g. ls, ssh). Or maybe the newest version added the -foo flag. And if you've got something like 'sed' overwriting the input file (-i), it'd better make sure the flags are exactly as documented.