4 ms·

I just have ~/bin/ and ~/bin/scripts/ and both are in my $PATH so I get autocompletion automatically. I usually don't create "--help" options for personal scri

by dheera 6y ago

I just have ~/bin/ and ~/bin/scripts/ and both are in my $PATH so I get autocompletion automatically. I usually don't create "--help" options for personal scripts. Most of my personal scripts are mostly designed to be extremely specific and be so damn obvious how to use them because the --help's of other commands are too complicated. Some examples of my scripts in ~/bin/scripts/: ffmpeg-extract-sound ffmpeg-jpegs-to-video ffmpeg-video-to-jpegs ffmpeg-ogv-to-mp4 convert-png-rgb24-to-grey8 iptables-ignore-rst-packets jabra-stop-changing-volume-goddamnit apt-remove-arm64-shit-that-nvidias-tx2-installer-installed-onto-my-x86-system ipv6-on ipv6-off ros-install-this etc.

lars_francke 6y ago
Asking for a friend: What does your "jabra-stop-changing-volume-goddamnit" script look like?
smichel17 6y ago
help-script(){ "${EDITOR:?vi}" "$(which "$1")"; } I don't actually use that but the point stands -- If the script is simple enough, you don't need a --help; comments in the source work just as well.
- OMGWTF 6y ago
  zsh has `= expansion`: > If a word begins with an unquoted `=' and the EQUALS option is set, the remainder of the word is taken as the name of a command. If a command exists by that name, the word is replaced by the full pathname of the command. To edit the source of `myscript` I can then use vim =myscript
  - ianthehenry 6y ago
    That's really neat! I'd never heard of that. I think you just saved my future self many many keystrokes.