I disagree. You can write shell scripts just fine and always set -euo pipefail * I'm not sure what you mean by four PATHs, but if you really mean to be using u

I disagree. You can write shell scripts just fine and always set -euo pipefail * I'm not sure what you mean by four PATHs, but if you really mean to be using unset variables for them, you should be using " ${V-}" or "${V:-}" syntax which does not fail. But again I don't know why you would do this other than maybe [[ "${1-}" ]] * Variable arguments are still trivial with $#. Check (($#>3)), use while (($#>0)), etc I also disagree that this is unproductive. With minor modifications/(adding :- or -), you can prevent a whole class of bugs (undefined variables). This woukd have prevent real-world issues such as in the post here as well as Steam when it wiped home directories since it ran (not sure the exact syntax) rm -rf $STEAMROOT/* with an unset variable