Bash Cheatsheet

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from Bash Cheatsheet

Bash Cheatsheet brings together common shell operations for navigating files, inspecting data, and composing commands. Bash combines commands with quoting, expansions, redirection, and pipelines. Understanding which part of a line is interpreted by the shell prevents many surprises, particularly when filenames contain spaces or a variable expands into several words. A cheatsheet works best as a memory aid while you practice a concrete task. Read the command or syntax together with its arguments, placeholders, and surrounding context. Similar-looking options can have very different meanings, and an example written for one platform or version may need adjustment elsewhere. Keep the reference beside a small test case, use read-only examples first when possible, and check the relevant help output before applying an unfamiliar command to valuable files or a running service.

Guide updated October 13, 2026

How to use this tool

1. Identify the operation you want to perform and find the matching section of the reference. Read the whole example before copying any part of it.
2. Find the relevant command family and try a read-only example in a temporary working directory.
3. Review the example below and compare its expected behavior with a small sample of your own input before continuing.
4. Try the adapted example on a small test case, compare the result with the explanation, and save the command with a note about the context in which it works.

SEE IT IN PRACTICE

A worked example

pwd

The absolute path of the shell's current working directory

This simple command establishes where relative paths will resolve before a more complex operation is attempted.

The shell interprets a command before the program does

Quoting, variable expansion, wildcard expansion, redirection, and pipelines are shell features. The program ultimately receives arguments after that interpretation, which explains why an unquoted filename containing a space can become two arguments. Single and double quotes have different expansion behavior. Practice with harmless text output and inspect the results before constructing a command that moves or deletes files. Understanding this boundary is more valuable than memorizing a long command that happens to work for one simple filename.

Build pipelines in observable stages

A pipeline is easier to debug when each stage has a clear input and output. Run the first command, inspect its result, then add the next transformation. Check how errors and exit status are handled instead of assuming visible output means the whole pipeline succeeded. Avoid using a reference's sample path unchanged, and establish the current directory before a relative-path operation. A script intended for reuse should make its assumptions about shell, files, and environment variables explicit.

When this tool is useful

• Review shell navigation commands
• Understand quoting and variable expansion
• Build a small repeatable shell workflow

Tips for a better result

• Check quoting, the current directory, and each pipeline stage separately before combining commands.
• Replace example paths, identifiers, and names deliberately. Copying a reference command unchanged can target a different file, branch, service, or environment from the one you intended.
• Keep the source and the settings used for this result together. That makes a later comparison or correction easier, especially when another person needs to reproduce the same outcome.

Frequently asked questions