Variables and Quoting

Published by Programming Line in Bash Shell Scripting. Last updated .

Bash variables store strings, and quoting controls how those strings are split and expanded. Most shell bugs come from losing the boundary between one value and several words, so double-quoting variable expansions is a foundational safety habit.

This lesson develops Variables and Quoting 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 Variables and Quoting Works

Bash expands parameter references before running a command. An unquoted expansion is eligible for word splitting and filename expansion; a double-quoted expansion remains one argument. Single quotes preserve text literally, while double quotes still allow parameter, command, and arithmetic expansion.

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

name='Ada Lovelace'
printf '%s\n' "$name"
printf '%s\n' '${name}'

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

student='Ada Lovelace'
track='shell scripting'
printf '%s is learning %s.\n' "$student" "$track"

Output:

Ada Lovelace is learning shell scripting.

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

price=25
quantity=4
printf 'Total: %d\n' "$((price * quantity))"
printf '%s\n' 'The literal text $price is not expanded.'

Output:

Total: 100
The literal text $price is not expanded.

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

  • Adding spaces around = in an assignment; Bash then treats the name as a command.
  • Writing $file without quotes when the value may contain spaces or wildcard characters.

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

  • Write "$variable" unless you intentionally want splitting.
  • Use descriptive lowercase names for script variables.
  • Use readonly for values that should not change.

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 Variables and Quoting 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

  • Variables and Quoting 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.