Shell Scripting / Bash Tricks

Stop dealing with messy bash arrays that break on spaces

🧩 The Challenge

You’ve probably tried to iterate over a list of filenames and watched your script explode because some genius decided to put a space in a directory name. It’s infuriating when a simple loop turns into a broken mess of escaped characters and shell expansion errors.

💡 The Fix

Switch from space-delimited strings to real bash arrays and use the correct globbing syntax to handle the files as actual objects. This stops the shell from mangling your data before your code even touches it.

mapfile -t my_files < <(find . -name "*.txt")
for file in "${my_files[@]}"; do
echo "Processing: $file"
done

⚙️ Why It Works

Using mapfile tells bash to read lines directly into an indexed array, which completely bypasses the weird word-splitting behavior you usually get with command substitution. And it handles newlines correctly, provided your filenames don’t contain them, which is a whole other rabbit hole.

🚀 Pro-Tip: If you actually have newlines in your filenames, use find -print0 and read -d ” to keep your sanity intact.

Linux Tips & Tricks | © ngelinux.com | 9/28/2026