Bash: Shell Options – Master set and shopt for Enhanced Script Behavior
Introduction to Bash Shell Options – Customize Behavior with set and shopt
Bash offers two powerful built-in tools—set and shopt—that let you configure shell behavior, debug scripts, and control execution flow. Whether you want to exit on error, enable extended globbing, or make your script more defensive, mastering these options is essential for writing reliable and secure Bash scripts.
In this article, you’ll learn:
- The difference between
setandshopt - Key flags like
set -e,set -u,shopt -s nullglob, etc. - How to enable/disable shell behaviors
- Real-world scenarios and debugging tricks
The set Built-in Command
The set command modifies shell options and positional parameters. Commonly used with flags like -e, -u, -x, and -o.
Common set Flags
| Option | Description |
|---|---|
-e | Exit immediately if any command returns non-zero |
-u | Treat unset variables as an error |
-x | Print each command as it executes (debugging) |
-o pipefail | Exit if any command in a pipeline fails |
-n | Parse script without running it (syntax check only) |
Example:
#!/bin/bash
set -eu -o pipefail
echo "This script is strict and safe."
Combine
-e,-u, and-o pipefailfor robust, production-ready scripts.
The shopt Built-in Command
The shopt (shell options) command enables/disables Bash-specific behaviors not handled by set.
Common shopt Options
| Option | Description |
|---|---|
nullglob | Globs that match nothing return null (empty string) |
dotglob | Wildcards match hidden (.) files too |
nocaseglob | Case-insensitive glob matching |
extglob | Enable extended pattern matching operators |
histappend | Append to history file instead of overwriting |
cdspell | Auto-correct minor typos in cd command |
Example:
shopt -s nullglob dotglob
files=(*.txt)
echo "${files[@]}"
Matches .hidden.txt too, and won’t error if no .txt files exist.
Example: Using set -u to Catch Unset Variables
#!/bin/bash
set -u
echo "User is: $USER"
echo "Home: $HOME"
echo "Unset var: $UNSET_VAR"
Output:
./script.sh: line 4: UNSET_VAR: unbound variable
This prevents bugs caused by typos or missing environment variables.
Example: Safe Pipelines with set -o pipefail
#!/bin/bash
set -o pipefail
grep "text" file.txt | sort | uniq
Script exits if grep fails—even if sort succeeds.
Example: Enable Extended Globbing with shopt -s extglob
shopt -s extglob
ls !(*.log|*.txt)
Lists files excluding .log and .txt using pattern negation.
Toggle Shell Options
- Enable:
set -e shopt -s nullglob - Disable:
set +e shopt -u nullglob
Summary – Bash set and shopt Options
The set and shopt commands let you tailor Bash behavior for safety, debugging, and enhanced scripting. They are critical tools for making scripts robust, secure, and user-friendly.
Key Takeaways:
- Use
set -euo pipefailfor safer scripting - Use
shoptfor pattern matching and shell usability enhancements - Toggle options on/off depending on the script’s purpose
Real-world Uses:
- Exit immediately on failure in CI/CD scripts
- Enable
nullglobto safely handle unmatched globs - Use
extglobto create advanced file filters
FAQ – Bash set and shopt Options
What’s the difference between set and shopt?
set handles core POSIX options and positional parameters. shopt configures Bash-specific features like globbing, history, and directory behavior.
What does set -e do?
It makes the script exit immediately if any command returns a non-zero exit code.
Why should I use set -o pipefail?
It ensures your script detects failure even if an earlier command in a pipeline fails silently.
How do I enable case-insensitive globbing?
Use:
shopt -s nocaseglob
Can I enable multiple set or shopt options at once?
Yes. Combine set options like:
set -euxo pipefail
And enable multiple shopt flags with multiple shopt -s commands.
Share Now :
