case and Option Parsing

The case statement matches one value against several shell patterns. It is ideal for subcommands, file extensions, yes/no answers, and small option parsers where a long if chain would hide the available choices.

This lesson develops case and Option Parsing from its underlying shell behavior through practical, runnable examples. The goal is not merely to memorize punctuation, but to understand what Bash expands, what it executes, and how to keep data boundaries intact.

How case and Option Parsing Works

Bash evaluates patterns from top to bottom and executes the first matching branch. The | character combines alternatives and * is the usual fallback. Each branch ends with ;; so matching stops before the next branch.

Bash processes source in stages: it parses the command, performs the relevant expansions, applies redirections, and finally runs a builtin, function, or external program. Quoting affects the expansion stage, while control structures react to exit statuses. Keeping these stages separate in your mental model makes debugging much faster.

Syntax

case $value in
  pattern) commands ;;
  other|alternative) commands ;;
  *) fallback ;;
esac

Whitespace and quoting are part of the language. Do not copy a compact example and then remove quotes or spaces casually: those characters often determine argument boundaries or separate reserved words. Use bash -n script.sh to check syntax without executing the script.

Worked Examples

Example 1: Core behavior

extension='json'
case $extension in
  json) printf 'Structured data\n' ;;
  jpg|png) printf 'Image file\n' ;;
  *) printf 'Other file\n' ;;
esac

Output:

Structured data

The first example keeps every expansion explicit and quotes values at the point where Bash builds the command’s arguments. Trace it one line at a time: assignments update shell state, expansions produce values, and printf receives a format plus distinct arguments.

Example 2: Practical composition

set -- --mode fast
mode='normal'
while (( $# > 0 )); do
  case $1 in
    --mode) mode=${2:?missing mode}; shift 2 ;;
    *) printf 'Unknown option: %s\n' "$1"; exit 2 ;;
  esac
done
printf 'Mode: %s\n' "$mode"

Output:

Mode: fast

The second example composes the feature with another shell capability. Its output is deterministic, so you can paste the script into a temporary file, run it, and compare every line. If your result differs, enable a trace locally and inspect the expanded arguments rather than guessing.

Execution Step by Step

1. Bash reads enough input to form a complete command or compound command.
2. Parameter, command, and arithmetic expansions are performed where the syntax requests them.
3. Quoting determines whether expanded text stays together as one argument.
4. Redirections are connected before the selected command runs.
5. The command returns an exit status, which a conditional, loop, or following command may use.

This sequence also explains why printing a variable can look correct even when passing it unquoted is unsafe: the destructive splitting happens while Bash constructs arguments, not while the value is stored.

Common Mistakes

• Forgetting shift in a parsing loop, which creates an infinite loop.
• Leaving out the fallback branch and silently accepting misspelled options.

Another common mistake is testing only the happy path. Shell programs interact with files, permissions, processes, and user-controlled strings. Always try an empty value, a value containing spaces, and a failing command. Those tests expose most quoting and error-handling defects early.

Best Practices

• Keep option names explicit and documented.
• Return exit status 2 for command-line usage errors.
• Use getopts when supporting standard short options.

For production automation, start scripts with a clear interpreter line, document inputs and outputs, keep functions small, and run ShellCheck. Strict settings can help, but explicit validation and purposeful error messages remain necessary.

Practice Exercises

• Recreate the first case and Option Parsing example without copying it, then change one input containing a space.
• Add one validation failure that prints a useful message to standard error and returns a non-zero status.
• Wrap the central behavior in a function and call it twice with different arguments.

Summary

• case and Option Parsing is easiest to use correctly when you track parsing, expansion, execution, and exit status separately.
• Quoted expansions preserve data boundaries and should be the default.
• Deterministic examples, syntax checks, and failure-path tests turn shell snippets into reliable automation.