Skip to main content

Reminder for #bash and #shell script authors:
wizardzines.com/comics/bash-er…
errors: by default, bash will continue after errors. Bash: oh, was that an error? who care, let's keep running! Programmer: Uh that is NOT what I wanted. set -e stops the script on errors. this makes your script WAY more predictable. by default, unset variables don't error. rm -rf "$HOME/$SOMEPTH". bash: $SOMEPTH doesn't exist? no problem, i'll just use an empty string! programmer: OH NOOO that means rm -rf $HOME. set -u stops the script on unset variables. bash: I've never heard of $SOMEPTH! STOP EVERYTHING!!! by default, a command failing doesn't fail the whole pipeline. curl yxqzq.ca | grep 'panda' bash: curl failed but grep succeeded so it's fine! success! set -o pipefail makes the pipe fail if any command fails. you can combine set -e, set -u and set -o pipefail into one command I put at the top of all my scripts: set -euo pipefail

bash errors

wizard zines
#shell #bash
⇧