We have all been there. You write a script to iterate over a list of files or server names, and suddenly it breaks because a single directory contains a space in its name. You spend an hour debugging, adding quotes everywhere, and it still fails. The culprit is almost always the Internal Field Separator, or IFS. It is the invisible force deciding how your shell splits strings, and it defaults to whitespace. When your input is not perfect, it destroys your logic.

Why your loops are probably lying to you

Most of us learn the for loop syntax and never stop to consider that the shell is tokenizing our input based on tabs, spaces, and newlines before our command even sees the arguments. If you are reading lines from a file or globbing results, the shell will treat each space as a separator. It is a classic foot-gun. You might think you are iterating over file names, but you are actually iterating over a fragmented list of words.

while IFS= read -r line; do process "$line"; done < input_file.txt

• Always set IFS= when reading lines to prevent leading or trailing whitespace trimming
• Use the -r flag with read to stop backslashes from being interpreted as escape characters
• Avoid using for loops for files because globbing is unpredictable with special characters
• Quote every variable reference to ensure the shell treats your strings as single atoms

Next time you are stuck parsing a list, skip the standard for loop construct entirely. Moving to a while-read loop is the only way to treat line-based input with the respect it deserves. If you ignore how your environment handles whitespace, you are just waiting for the day a colleague names a directory with a space and ruins your production deploy. Set the IFS locally inside your loop if you really have to, but keep it tight and move on.