This question already has an answer here:

I wrote the following script to diff the outputs of two directores with all the same files in them as such:


for file in `find . -name "*.csv"`  
     echo "file = $file";
     diff $file /some/other/path/$file;
     read char;

I know there are other ways to achieve this. Curiously though, this script fails when the files have spaces in them. How can I deal with this?

Example output of find:

./zQuery - abc - Do Not Prompt for Date.csv

marked as duplicate by Gilles bash Dec 10 '17 at 5:44

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 2
    I disagree with that this would be a duplicate. The accepted answer answers how to loop over filenames with spaces; that has nothing to do with "why is looping over find's output bad practise". I found this question (not the other) because I need to loop over filenames with spaces, as in: for file in $LIST_OF_FILES; do ... where $LIST_OF_FILES is not the output of find; it's just a list of filenames (separated by newlines). – Carlo Wood Feb 14 at 1:58

10 Answers 10

up vote 158 down vote accepted

Short answer (closest to your answer, but handles spaces)

for file in `find . -type f -name "*.csv"`  
     echo "file = $file"
     diff "$file" "/some/other/path/$file"
     read line

Better answer (also handles wildcards and newlines in file names)

find . -type f -name "*.csv" -print0 | while IFS= read -r -d '' file; do
    echo "file = $file"
    diff "$file" "/some/other/path/$file"
    read line </dev/tty

Best answer (based on Gilles' answer)

find . -type f -name '*.csv' -exec sh -c '
  echo "$file"
  diff "$file" "/some/other/path/$file"
  read line </dev/tty
' {} ';'

Or even better, to avoid running one sh per file:

find . -type f -name '*.csv' -exec sh -c '
  for file do
    echo "$file"
    diff "$file" "/some/other/path/$file"
    read line </dev/tty
' sh {} +

Long answer

You have three problems:

  1. By default, the shell splits the output of a command on spaces, tabs, and newlines
  2. Filenames could contain wildcard characters which would get expanded
  3. What if there is a directory whose name ends in *.csv?

1. Splitting only on newlines

To figure out what to set file to, the shell has to take the output of find and interpret it somehow, otherwise file would just be the entire output of find.

The shell reads the IFS variable, which is which is set to <space><tab><newline> by default.

Then it looks at each character in the output of find. As soon as it sees any character that's in IFS, it thinks that marks the end of the file name, so it sets file to whatever characters it saw until now and runs the loop. Then it starts where it left off to get the next file name, and runs the next loop, etc., until it reaches the end of output.

So it's effectively doing this:

for file in "zquery" "-" "abc" ...

To tell it to only split the input on newlines, you need to do


before your for ... find command.

That sets IFS to a single newline, so it only splits on newlines, and not spaces and tabs as well.

If you are using sh or dash instead of ksh93, bash or zsh, you need to write IFS=$'\n' like this instead:


That is probably enough to get your script working, but if you're interested to handle some other corner cases properly, read on...

2. Expanding $file without wildcards

Inside the loop where you do

diff $file /some/other/path/$file

the shell tries to expand $file (again!).

It could contain spaces, but since we already set IFS above, that won't be a problem here.

But it could also contain wildcard characters such as * or ?, which would lead to unpredictable behavior. (Thanks to Gilles for pointing this out.)

To tell the shell not to expand wildcard characters, put the variable inside double quotes, e.g.

diff "$file" "/some/other/path/$file"

The same problem could also bite us in

for file in `find . -name "*.csv"`

For example, if you had these three files


(very unlikely, but still possible)

It would be as if you had run

for file in file1.csv file2.csv *.csv

which will get expanded to

for file in file1.csv file2.csv *.csv file1.csv file2.csv

causing file1.csv and file2.csv to be processed twice.

Instead, we have to do

find . -name "*.csv" -print | while IFS= read -r file; do
    echo "file = $file"
    diff "$file" "/some/other/path/$file"
    read line </dev/tty

read reads lines from standard input, splits the line into words according to IFS and stores them in the variable names that you specify.

Here, we're telling it not to split the line into words, and to store the line in $file.

Also note that read line has changed to read line </dev/tty.

This is because inside the loop, standard input is coming from find via the pipeline.

If we just did read, it would be consuming part or all of a file name, and some files would be skipped.

/dev/tty is the terminal where the user is running the script from. Note that this will cause an error if the script is run via cron, but I assume this is not important in this case.

Then, what if a file name contains newlines?

We can handle that by changing -print to -print0 and using read -d '' on the end of a pipeline:

find . -name "*.csv" -print0 | while IFS= read -r -d '' file; do
    echo "file = $file"
    diff "$file" "/some/other/path/$file"
    read char </dev/tty

This makes find put a null byte at the end of each file name. Null bytes are the only characters not allowed in file names, so this should handle all possible file names, no matter how weird.

To get the file name on the other side, we use IFS= read -r -d ''.

Where we used read above, we used the default line delimiter of newline, but now, find is using null as the line delimiter. In bash, you can't pass a NUL character in an argument to a command (even builtin ones), but bash understands -d '' as meaning NUL delimited. So we use -d '' to make read use the same line delimiter as find. Note that -d $'\0', incidentally, works as well, because bash not supporting NUL bytes treats it as the empty string.

To be correct, we also add -r, which says don't handle backslashes in file names specially. For example, without -r, \<newline> are removed, and \n is converted into n.

A more portable way of writing this that doesn't require bash or zsh or remembering all the above rules about null bytes (again, thanks to Gilles):

find . -name '*.csv' -exec sh -c '
  echo "$file"
  diff "$file" "/some/other/path/$file"
  read char </dev/tty
' {} ';'

3. Skipping directories whose names end in *.csv

find . -name "*.csv"

will also match directories that are called something.csv.

To avoid this, add -type f to the find command.

find . -type f -name '*.csv' -exec sh -c '
  echo "$file"
  diff "$file" "/some/other/path/$file"
  read line </dev/tty
' {} ';'

As glenn jackman points out, in both of these examples, the commands to execute for each file are being run in a subshell, so if you change any variables inside the loop, they will be forgotten.

If you need to set variables and have them still set at the end of the loop, you can rewrite it to use process substitution like this:

while IFS= read -r -d '' file; do
    echo "file = $file"
    diff "$file" "/some/other/path/$file"
    read line </dev/tty
done < <(find . -type f -name '*.csv' -print0)
echo "$i files processed"

Note that if you try copying and pasting this at the command line, read line will consume the echo "$i files processed", so that command won't get run.

To avoid this, you could remove read line </dev/tty and send the result to a pager like less.


I removed the semi-colons (;) inside the loop. You can put them back if you want, but they are not needed.

These days, $(command) is more common than `command`. This is mainly because it's easier to write $(command1 $(command2)) than `command1 \`command2\``.

read char doesn't really read a character. It reads a whole line so I changed it to read line.

  • 2
    putting while in a pipeline can create issues with the subshell created (variables in the loop block not visible after the command completes for example). With bash, I would use input redirection and process substitution: while read -r -d $'\0' file; do ...; done < <(find ... -print0) – glenn jackman Mar 18 '11 at 1:23
  • Sure, or using a heredoc: while read; do; done <<EOF "$(find)" EOF. Not so easy to read however. – Mikel Mar 18 '11 at 1:41
  • @glenn jackman: I tried to add more explanation just now. Did I just make it better or worse? – Mikel Mar 18 '11 at 2:36
  • You don't need IFS, -print0, while and read if you handle find to its full, as shown below in my solution. – user unknown Mar 19 '11 at 23:10
  • 1
    Your first solution will cope with any character except newline if you also turn off globbing with set -f. – Gilles Apr 4 '11 at 19:28

This script fails if any file name contains spaces or shell globbing characters \[?*. The find command outputs one file name per line. Then the command substitution `find …` is evaluated by the shell as follows:

  1. Execute the find command, grab its output.
  2. Split the find output into separate words. Any whitespace character is a word separator.
  3. For each word, if it is a globbing pattern, expand it to the list of files it matches.

For example, suppose there are three files in the current directory, called `foo* bar.csv, foo 1.txt and foo 2.txt.

  1. The find command returns ./foo* bar.csv.
  2. The shell splits this string at the space, producing two words: ./foo* and bar.csv.
  3. Since ./foo* contains a globbing metacharacter, it's expanded to the list of matching files: ./foo 1.txt and ./foo 2.txt.
  4. Therefore the for loop is executed successively with ./foo 1.txt, ./foo 2.txt and bar.csv.

You can avoid most problems at this stage by toning down word splitting and turning off globbing. To tone down word splitting, set the IFS variable to a single newline character; this way the output of find will only be split at newlines and spaces will remain. To turn off globbing, run set -f. Then this part of the code will work as long as no file name contains a newline character.

set -f
for file in $(find . -name "*.csv"); do …

(This isn't part of your problem, but I recommend using $(…) over `…`. They have the same meaning, but the backquote version has weird quoting rules.)

There's another problem below: diff $file /some/other/path/$file should be

diff "$file" "/some/other/path/$file"

Otherwise, the value of $file is split into words and the words are treated as glob patterns, like with the command substitutio above. If you must remember one thing about shell programming, remember this: always use double quotes around variable expansions ($foo) and command substitutions ($(bar)), unless you know you want to split. (Above, we knew we wanted to split the find output into lines.)

A reliable way of calling find is telling it to run a command for each file it finds:

find . -name '*.csv' -exec sh -c '
  echo "$0"
  diff "$0" "/some/other/path/$0"
' {} ';'

In this case, another approach is to compare the two directories, though you have to explicitly exclude all the “boring” files.

diff -r -x '*.txt' -x '*.ods' -x '*.pdf' … . /some/other/path
  • I'd forgotten about wildcards as another reason to quote properly. Thanks! :-) – Mikel Mar 18 '11 at 2:34
  • instead of find -exec sh -c 'cmd 1; cmd 2' ";", you should use find -exec cmd 1 {} ";" -exec cmd 2 {} ";", because the shell needs to mask the parameters, but find doesn't. In the special case here, echo "$0" doesn't need to be a part of the script, just append -print after the ';'. You didn't include a question to proceed, but even that can be done by find, as shown below in my soulution. ;) – user unknown Mar 19 '11 at 23:25
  • 2
    @userunknown: The use of {} as a substring of a parameter in find -exec is not portable, that's why the shell is needed. I don't understand what you mean by “the shell needs to mask the parameters”; if it's about quoting, my solution is properly quoted. You're right that the echo part could be performed by -print instead. -okdir is a fairly recent GNU find extension, it's not available everywhere. I didn't include the wait to proceed because I consider that extremely poor UI and the asker can easily put read in the shell snippet if he wants. – Gilles Mar 19 '11 at 23:59
  • Quoting is a form of masking, isn't it? I don't understand your remark about what is portable, and what not. Your example (2nd from bottom) uses -exec to invoke sh and uses {} - so where is my example (beside -okdir) less portable? find . -name "*.csv" -exec diff {} /some/other/path/{} ";" -print – user unknown Mar 20 '11 at 1:05
  • 2
    “Masking” isn't common terminology in shell literature, so you'll have to explain what you mean if you want to be understood. My example uses {} only once and in a separate argument; other cases (used twice or as a substring) are not portable. “Portable” means that it'll work on all unix systems; a good guideline is the POSIX/Single Unix specification. – Gilles Mar 20 '11 at 1:15

Afaik find has all you need.

find . -okdir diff {} /some/other/path/{} ";"

find takes itself care for calling the programs savely. -okdir will prompt you before the diff (are you sure yes/no).

No shell involved, no globbing, jokers, pi, pa, po.

As a sidenote: If you combine find with for/while/do/xargs, in most cases, you're doing it wrong. :)

  • Thanks for the answer. Why are you doing it wrong if you combine find with for/while/do/xargs? – Amir Afghani Mar 18 '11 at 14:56
  • 1
    Find already iterates over a subset of files. Most people who show up with questions could just use one of the actions (-ok(dir) -exec(dir), -delete) in combination wiht ";" or + (later for parallel invocation). The main reason to do so, is, that you don't have to fiddle around with file parameters, masking them for the shell. Not that important: You needn't new processes all the time, less memory, more speed. shorter program. – user unknown Mar 18 '11 at 21:05
  • Not here to crush your spirit, but compare: time find -type f -exec cat "{}" \; with time find -type f -print0 | xargs -0 -I stuff cat stuff. The xargs version was faster by 11 seconds when processing 10000 empty files. Be careful when asserting that in most cases combining find with other utilities is wrong. -print0 and -0 are there to deal with spaces in the file names by using a zero byte as the item separator rather than a space. – Jonathan Komar Jul 5 '17 at 11:00
  • @JonathanKomar: Your find/exec commando took 11.7 s on my system with 10.000 files, the xargs version 9.7 s, time find -type f -exec cat {} + as suggested in my previous comment took 0.1 s. Note the subtile difference between "it is wrong" and "you're doing it wrong", especially when decorated with a smilie. Did you, for instance, do it wrong? ;) BTW, spaces in the filename are no problem for the above command and find in general. Cargo cult programmer? And by the way, combining find with other tools is fine, just xargs is most of the time superflous. – user unknown Jul 5 '17 at 12:48
  • @userunknown I explained how my code deals with spaces for posterity (education of future viewers), and was not implying that your code does not. The + for parallel calls is very fast, as you mentioned. I would not say cargo cult programmer, because this ability to use xargs in this way comes in handy on numerous occasions. I agree more with the Unix philosophy: do one thing and do it well (use programs separately or in combination to get a job done). find is walking a fine line there. – Jonathan Komar Jul 6 '17 at 7:21

Loop through any files (any special character included) with the completely safe find (see the link for documentation):

exec 9< <( find "$absolute_dir_path" -type f -print0 )
while IFS= read -r -d '' -u 9
    file_path="$(readlink -fn -- "$REPLY"; echo x)"
    echo "START${file_path}END"
  • Thanks for mentioning -d ''. I didn't realize that $'\0' was the same as '', but it seems to be. Good solution, as well. – Mikel Apr 4 '11 at 11:30
  • I like the decoupling of find and while, thanks. – dhill Apr 11 '13 at 16:32
  • dammit l0b0, why do I always end up finding your solutions on SE? ;) – Dominik R Feb 3 '17 at 13:07
  • Dammit @DominikR, now there's at least two more things I don't know - why you always end up finding my solutions and why you asked me to answer that :p – l0b0 Feb 3 '17 at 19:00

I'm surprised nobody mentioned the obvious zsh solution here yet:

for file (**/*.csv(ND.)) {
  do-something-with $file

((D) to also include hidden files, (N) to avoid the error if there's no match, (.) to restrict to regular files.)

bash4.3 and above now supports it partially as well:

shopt -s globstar nullglob dotglob
for file in **/*.csv; do
  [ -f "$file" ] || continue
  [ -L "$file" ] && continue
  do-something-with "$file"

File names with spaces in them look like multiple names on the command line if they're not quoted. If your file is named "Hello World.txt", the diff line expands to:

diff Hello World.txt /some/other/path/Hello World.txt

which looks like four file names. Just put quotes around the arguments:

diff "$file" "/some/other/path/$file"
  • This helps but it doesn't solve my problem. I still see cases where the file is being split up into multiple tokens. – Amir Afghani Mar 18 '11 at 0:37
  • This answer is misleading. The problem is the for file in `find . -name "*.csv"` command. If there is a file called Hello World.csv, file will be set to ./Hello and then to World.csv. Quoting $file won't help. – G-Man Mar 4 '15 at 19:11

Double quoting is your friend.

diff "$file" "/some/other/path/$file"

Otherwise the variable's contents get word-split.

  • 1
    This is misleading. The problem is the for file in `find . -name "*.csv"` command. If there is a file called Hello World.csv, file will be set to ./Hello and then to World.csv. Quoting $file won't help. – G-Man Mar 4 '15 at 19:11

With bash4, you can also use the builtin mapfile function to set an array containing each lines and iterate on this array.

$ tree 
├── a
│   ├── a 1
│   └── a 2
├── b
│   ├── b 1
│   └── b 2
└── c
    ├── c 1
    └── c 2

3 directories, 6 files
$ mapfile -t files < <(find -type f)
$ for file in "${files[@]}"; do
> echo "file: $file"
> done
file: ./a/a 2
file: ./a/a 1
file: ./b/b 2
file: ./b/b 1
file: ./c/c 2
file: ./c/c 1

I'm surprised to not see readarray mentioned. It makes this very easy when used in combination with the <<< operator:

$ touch oneword "two words"

$ readarray -t files <<<"$(ls)"

$ for file in "${files[@]}"; do echo "|$file|"; done
|two words|

Using the <<<"$expansion" construct also allows you to split variables containing newlines into arrays, like:

$ string=$(dmesg)
$ readarray -t lines <<<"$string"
$ echo "${lines[0]}"
[    0.000000] Initializing cgroup subsys cpuset

readarray has been in Bash for years now, so this should probably be the canonical way to do this in Bash.

The spaces in the values can be avoided by as simple for loop construct

for CHECK_STR in `ls -l /root/somedir`

ls -l root/somedir contains my file with spaces

Output of above my file with spaces

to avoid this output, simple solution (notice the double quotes)

for CHECK_STR in "`ls -l /root/somedir`"

output my file with spaces

tried on bash

  • “Looping through files” – that is what the question says. Your solution will output the entire ls -l output at once. It is effectively equivalent with echo "CHECKSTR `ls -l /root/somedir`". – manatwork May 13 '13 at 7:02

Not the answer you're looking for? Browse other questions tagged or ask your own question.