Wildcards & Globbing in Linux Deep Cli Guide

A deep, practical, and system-level guide to understanding wildcards (globbing) in the Linux Command Line Interface. This guide goes far beyond basic usage to explain how globbing really works, how shells differ, pitfalls, performance, and professional shell workflows.

What Wildcards really Are

Wildcards are pattern-matching characters expanded by the shell itself, not by commands like ls, cp, or rm.

Example:

ls *.txt

What actually happens:

shell expands *.txt → file1.txt file2.txt
ls file1.txt file2.txt

⚠ Commands never see wildcards — they only receive expanded filenames.

Globbing vs Regular Expressions

Example confusion:

ls .*txt      # glob
ls | grep .*txt  # regex

Expansion Order (very Important)

Shell expansion happens in a defined order:

1. Brace expansion {}

2. Tilde expansion ~

3. Parameter expansion $VAR

4. Command substitution $( )

5. Pathname expansion (globbing)

6. Quote removal

This affects correctness and safety.

Types of Wildcards (deep Dive)

Asterisk *

• Matches zero or more characters

• Does NOT cross directory separators (/)

*.log
backup*

Question Mark ?

• Matches exactly one character

file?.txt   # file1.txt ✅ | file10.txt ❌

Character Classes [ ]

file[1-3].txt
file[a-z].txt

Advanced:

file[!0-9].txt   # NOT digits

Brace Expansion {} (not a Wildcard!)

Brace expansion generates strings before globbing.

echo file{1,2,3}.txt

Output:

file1.txt file2.txt file3.txt

Ranges:

echo {a..d}
echo {01..10}

Advanced Globbing Patterns

Enable extended globbing:

shopt -s extglob

Patterns:

*.!(txt)      # anything except txt
*@(jpg|png)

Requires Bash or Zsh.

Hidden Files & Dotfiles

• * ✅ does NOT match .hidden

• .* ✅ matches dotfiles

• .* ⚠ also matches . and ..

Safe pattern:

ls .[^.]*

Recursive Globbing **

Enable:

shopt -s globstar

Example:

ls **/*.c

Equivalent (conceptually):

find . -name "*.c"

Wildcards with Common Commands

cp *.txt /backup/
rm report[0-9].txt
mv *.log old_logs/
chmod +x *.sh

Always test first:

echo rm *.log

Wildcards vs find

Best practice:

• Use globs for simple cases

• Use find for complex logic

Quoting & Escaping

Disable Expansion Completely:

echo "*.txt"

Escape a Single Wildcard:

echo \*.txt

Why important:

rm "$file"

Safety Techniques (very Important)

Dry Run Everything:

echo rm *.log

Fail on No Matches:

shopt -s failglob

Prevent Dangerous Deletes:

rm -- -file.txt

Performance Considerations

• Globbing happens before execution

• Large directories = memory expansion cost

• Use find for thousands of files

Shell limits:

getconf ARG_MAX

Shell Differences

Real-world Use Cases

Cleanup Logs:

rm /var/log/*.{1,old}

Project Setup:

mkdir -p app/{src,bin,docs,tests}

Batch Rename Preview:

echo mv *.jpeg *.jpg

Common Mistakes

❌ Believing commands interpret wildcards ❌ Forgetting hidden files ❌ Mixing regex with glob syntax ❌ Unquoted variables

Exercises

Beginner:

ls *.txt

Intermediate:

find . -name "*.log" -mtime -3

Advanced:

shopt -s globstar extglob
ls **/*.!(*.tmp)

✅ This guide is designed for Linux users, sysadmins, DevOps engineers, and shell scripters.

Understanding globbing gives you precision, safety, and speed at the command line.

Happy hacking 🐧