Master Linux Shell Wildcards: Why * Can Fail and How to Use Them Correctly

Linux Shell Wildcards and Metacharacters

Shell wildcards (also called glob patterns) are processed by the shell, not by the individual commands. They appear only in command arguments and are expanded by the shell into matching file names before the command runs. If no match is found, the pattern is passed unchanged as a literal argument.

Example:

ls a.txt b.txt c.old

In this case the pattern *.txt matches a.txt and b.txt, so the command actually executed is ls a.txt b.txt. When a pattern such as d*.txt finds no files, the shell leaves it unchanged, resulting in an error like “cannot access d*.txt: No such file or directory”.

1. Common Shell Wildcards

The most frequently used wildcards are *, ?, [], and {}. They resemble regular‑expression syntax but operate differently and should not be confused.

2. Shell Metacharacters (Special Characters)

Beyond wildcards, the shell defines metacharacters that separate words or control command flow, such as |, &, ;, ( ), < >, and whitespace. These characters affect command parsing rather than filename matching.

3. Shell Escape Characters

To treat a wildcard or metacharacter as a literal, you can use one of three quoting mechanisms: the backslash escape, single quotes, or double quotes. The escape character (\) disables the special meaning of the following character.

Example with escaped wildcard:

ls '\*.txt'

The pattern is no longer expanded, so the command attempts to list a file literally named *.txt and fails if it does not exist.

4. Shell Script Parsing Process

When the shell receives a command line, it performs a series of steps: tokenization, alias expansion, parameter expansion, command substitution, arithmetic expansion, word splitting, pathname expansion (wildcard expansion), and finally execution. Quoting influences which steps are performed. Double quotes skip only the pathname expansion step, while single quotes skip all expansions, passing the text directly to the command.