set -u for undefined variable errors in Bash Scripting

Introduction

Using set -u helps catch mistakes by stopping the script when you use a variable that has not been set. This prevents unexpected errors later.

When you want to avoid bugs caused by typos in variable names.

When writing scripts that depend on variables being set before use.

When debugging scripts to find missing or unset variables quickly.

When you want your script to fail fast instead of continuing with wrong data.

Syntax

Bash Scripting

set -u

This command makes the shell treat unset variables as errors.

It is often used at the start of a script for safer scripting.

Examples

This script will stop with an error because MY_VAR is not set.

Bash Scripting

set -u

# Using an unset variable causes an error

echo "$MY_VAR"

This script prints 'Hello' because MY_VAR is set.

Bash Scripting

set -u

MY_VAR="Hello"
echo "$MY_VAR"

This prints 'default' if MY_VAR is not set, avoiding an error.

Bash Scripting

set -u

# Using default value to avoid error

echo "${MY_VAR:-default}"

Sample Program

This script will stop with an error if NAME is not set because of set -u. If you set NAME, it will greet the person.

Bash Scripting

#!/bin/bash
set -u

# Uncomment the next line to set the variable
# NAME="Alice"

echo "Hello, $NAME!"

Important Notes

Use ${VAR:-default} to provide a default value and avoid errors with set -u.

set -u helps catch bugs early but can stop scripts unexpectedly if variables are missing.

Combine set -u with set -e for safer scripts that stop on errors and unset variables.

Summary

set -u stops the script if you use a variable that is not set.

It helps find mistakes like typos or missing variables early.

Use default values with ${VAR:-value} to avoid errors when variables might be unset.