Combining Commands: Semicolons (;), &&, || & Subshells

In Plain English

Chaining multiple commands allows building expressive workflows. Semicolons (`;`) execute sequentially regardless of failure; `&&` executes the next command only if previous succeeded; `||` executes only on failure; and parentheses `( cmd1; cmd2 )` isolate execution inside an ephemeral subshell.

The Mental Model

"`&&` is like a safety lock: "If the door unlocks (success), walk inside." `;` is blind walking: "Turn left, then step forward, even if you bumped into a wall.""

Deep Dive: How It Works

Sequential Chaining (`;`): `mkdir dir; cd dir` runs `cd` even if `mkdir` fails.

Conditional AND (`&&`): `mkdir -p dir && cd dir` runs `cd` only if `mkdir` succeeds.

Conditional OR (`||`): `ping -c 1 host || echo "Host Down"` runs only if `ping` fails.

Subshells `( ... )` vs Grouping `{ ...; }`: Subshells spawn a child process isolating environment changes; braces execute inside current shell.

Syntax Blueprint

command1 && command2 || handle_error
( cd /tmp && ./build.sh ) # Current working directory stays unchanged
{ echo "Header"; cat body.txt; } > document.txt

Use && for dependable chaining and subshells ( ) to protect current working directory.

Core Rules to Remember

Guarded Chaining: `cd /target/dir && rm -rf *` guarantees you never wipe the wrong directory if cd fails.

Subshell Isolation: Environment variables and directory changes inside `( ... )` vanish upon exit.

Grouped Redirection: `{ cmd1; cmd2; } > output.txt` redirects multiple commands to a single destination file.

Common Beginner Traps & How to Fix Them

Mistake:Writing `cd /project/build; rm -rf *` without `&&`.

Why it happens: If `/project/build` does not exist, `cd` fails and `rm -rf *` wipes whatever directory you were currently sitting in.

How to fix: ALWAYS chain directory switches with `&&`: `cd /project/build && rm -rf *`.

Pro Tip: Inside braces `{ cmd1; cmd2; }`, POSIX requires a space after `{` and a trailing semicolon `;` before `}`.

Live Interactive Example

Hit Run Code to see it live

Subshell Isolation and Chained Execution

Git 2.45 / CLI

Output Console

Click "Run Code" to view the rendered output.

How it works: The subshell changed to /tmp without altering the parent script working directory.

Your Turn: Micro Challenge

No pressure! Edit the starter code below and test your solution with instant feedback.

Micro Exercise

Chain Success with &&

Echo "Step 1" and chain `&& echo "Step 2"`.

Sandbox Output

Click "Run & Check" to test your solution.

Finished reading and practicing?

Mark this lesson as completed to update your course progress.