Shell Scripting / Bash Tricks

Stop your bash loops from losing variables in pipes

🧩 The Challenge

You finally wrote a clean loop to process a file, but then you realized your counter or total variable is completely empty as soon as the loop ends. Spent way too long debugging that scope issue before realizing pipes start subshells.

💡 The Fix

Use process substitution instead of a pipe so the loop stays in the current shell context. It keeps your variables alive and lets you actually use the results of your hard work.

while read -r line; do ((count++)); done < <(cat your_data_file.txt)
echo "Total processed: $count"

⚙️ Why It Works

The <(command) syntax creates a named pipe or file descriptor that the shell feeds into your loop, effectively bypassing the subshell trigger that standard | pipes create. Because it’s still running in the parent shell, your variables don’t get tossed out once the process closes.

🚀 Pro-Tip: Use this with set -e and you’ll catch failures inside those loops much faster.

Linux Tips & Tricks | © ngelinux.com | 10/1/2026