While I agree with the guide, there is one thing I was missing while writing bash scripts with 'set -e' and that was some kind of stack tracing. So I added a ni

While I agree with the guide, there is one thing I was missing while writing bash scripts with 'set -e' and that was some kind of stack tracing. So I added a nice trap function to my personal bash script template. Be aware, that this version does not include all best practices described in the guide. #!/usr/bin/env bash #-------------------------------------------- # Default Bash Script Header set -eu trap stacktrace EXIT function stacktrace { if [ $? != 0 ]; then echo -e "\nThe command '$BASH_COMMAND' triggerd a stacktrace:" for i in $(seq 1 $((${#FUNCNAME[@]} - 2))); do j=$(($i+1)); echo -e "\t${BASH_SOURCE[$i]}: ${FUNCNAME[$i]}() called in ${BASH_SOURCE[$j]}:${BASH_LINENO[$i]}"; done fi } SCRIPT_DIR="$(dirname "$(readlink -f "$0")")" #--------------------------------------------