We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I would add set -u into your advice for set -eo pipefail, i.e. set -euo pipefail
set -u
set -eo pipefail
set -euo pipefail
An enhancement to that is to fail early in a script with useful feedback.
: ${FOO:?You have not set the FOO variable}
The text was updated successfully, but these errors were encountered:
I have mixed feelings about set -e in a library script with a lot of functions that do something like
set -e
is_integer() { [[ $1 =~ ^[-0-9][1-9]*$ ]] }
…but totally agree that -u needs to be in there 100% of the time.
-u
Sorry, something went wrong.
Mention set -u and ${arg:?message}
5bcd88a
Closes progrium#29 and progrium#37
aeb6be7
Closes progrium#29. Closes progrium#37.
No branches or pull requests
I would add
set -u
into your advice forset -eo pipefail
, i.e.set -euo pipefail
An enhancement to that is to fail early in a script with useful feedback.
The text was updated successfully, but these errors were encountered: