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
Bash has a lot of implicit semantics for non-existent variables. This can cause competing directives (like $OMP) to be eaten silently.
Setting a stricter mode for bash by default can help a lot.
set -e # Abort on first error set -u # Err on undefined variable set -o pipefail # Err on redirection failure
This would be a breaking change. The zpp standard library is not set -u safe. See gysela merge !633 for a few examples.
set -u
The text was updated successfully, but these errors were encountered:
I fully agree with set -u and -o pipefail. Regarding -e however, this breaks some perfectly valid patterns like:
-o pipefail
-e
dosomething if $?; then ...
Sorry, something went wrong.
No branches or pull requests
Bash has a lot of implicit semantics for non-existent variables.
This can cause competing directives (like $OMP) to be eaten silently.
Setting a stricter mode for bash by default can help a lot.
This would be a breaking change. The zpp standard library is not
set -u
safe.See gysela merge !633 for a few examples.
The text was updated successfully, but these errors were encountered: