> set -o errexit Unfortunately, `errexit` is fairly subtle. For example [ "${some_var-}" ] && do_something is a standard way to `do_something` only when

> set -o errexit Unfortunately, `errexit` is fairly subtle. For example [ "${some_var-}" ] && do_something is a standard way to `do_something` only when `some_var` is empty. With `errexit`, naively, this should fail, since `false && anything` is always false. However, `errexit` in later versions of Bash (and dash?) ignore this case, since the idiom is nice. However! If that's the last line of a function, then the function's return code will inherit the exit code of that line, meaning that f(){ [ "${some_var-}" ] && do_something;}; f will actually trigger `errexit` when `some_var` is empty, despite the code being functionally equivalent to the above, non-wrapped call. Anyway, there are a few subtleties like this that are worth being aware of. This is a good, but dated, reference: https://mywiki.wooledge.org/BashFAQ/105 https://mywiki.wooledge.org/BashFAQ/105