>> I agree. However, unfortunately it seems that by default Bash ignores>> all such errors and happily proceeds, unless you manually suffix every>> single command with an explicit return-code check.>> #!/bin/bash -e>> Have fun!
I think you mean "set -e", but anyway...
