Differences between revisions 21 and 22
Revision 21 as of 2010-04-15 15:39:31
Size: 3089
Editor: GreyCat
Comment: link to IFS, fix BashGuide links
Revision 22 as of 2010-07-30 07:21:51
Size: 3468
Editor: Lhunath
Comment: Link to Arguments.
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The preferred method is still to use [[UsingFind|find(1)]]:
Line 5: Line 4:
First and foremost; to understand why you're having trouble in the first place, read [[Arguments]] to get a grasp on how the shell understands the statements you give it. It is vital that you grasp this matter well if you're going to be doing anything with the shell.

The preferred method to deal with filenames is still to use [[UsingFind|find(1)]]:
Line 8: Line 10:
or, if you need to handle filenames ''en masse'', with GNU and recent BSD tools:
Line 10: Line 11:
or, if you need to handle filenames ''en masse'':
{{{
    find ... -exec command {} +
}}}

`xargs` is rarely ever more useful than the above, but if you ''really'' insist, remember to use `-0`:
Line 13: Line 20:
or with POSIX {{{find}}}:
Line 15: Line 21:
{{{
    find ... -exec command {} +
}}}
Use that unless you really can't.
Use one of these unless you ''really'' can't.
Line 20: Line 23:
Another way to deal with files with spaces in their names is to use the shell's filename expansion ([[globbing]]). This has the disadvantage of not working recursively (except with zsh's extensions), but if you just need to process all the files in a single directory, it works fantastically well. Another way to deal with files with spaces in their names is to use the shell's filename expansion ([[globbing]]). This has the disadvantage of not working recursively (except with zsh's extensions or bash 4's globstar), but if you just need to process all the files in a single directory, it works fantastically well.
Line 34: Line 37:
for file in ./*\ *; do for file in ./*' '*; do
Line 36: Line 39:
instead of *.mp3. instead of `*.mp3`.

How can I find and deal with file names containing newlines, spaces or both?

First and foremost; to understand why you're having trouble in the first place, read Arguments to get a grasp on how the shell understands the statements you give it. It is vital that you grasp this matter well if you're going to be doing anything with the shell.

The preferred method to deal with filenames is still to use find(1):

    find ... -exec command {} \;

or, if you need to handle filenames en masse:

    find ... -exec command {} +

xargs is rarely ever more useful than the above, but if you really insist, remember to use -0:

    find ... -print0 | xargs -0 command

Use one of these unless you really can't.

Another way to deal with files with spaces in their names is to use the shell's filename expansion (globbing). This has the disadvantage of not working recursively (except with zsh's extensions or bash 4's globstar), but if you just need to process all the files in a single directory, it works fantastically well.

This example changes all the *.mp3 files in the current directory to use underscores in their names instead of spaces. It uses Parameter Expansions that will not work in the original BourneShell or POSIX shell, but should be good in KornShell and BASH.

for file in ./*.mp3; do
    mv "$file" "${file// /_}"
done

Remember, you need to quote all your Parameter Expansions using double quotes. If you don't, the expansion will undergo WordSplitting (see also argument splitting and BashPitfalls). Also, always prefix globs with "./"; otherwise, if there's a file with "-" as the first character, the expansions might be misinterpreted as options.

You could do the same thing for all files with spaces in their names (regardless of extension) by using

for file in ./*' '*; do

instead of *.mp3.

Another way to handle filenames recursively involves using the -print0 option of find (a GNU/BSD extension), together with bash's -d option for read:

# Bash
unset a i
while IFS= read -r -d $'\0' file; do
  a[i++]="$file"        # or however you want to process each file
done < <(find /tmp -type f -print0)

The preceding example reads all the files under /tmp (recursively) into an array, even if they have newlines or other whitespace in their names, by forcing read to use the NUL byte (\0) as its line delimiter. Since NUL is not a valid byte in Unix filenames, this is the safest approach besides using find -exec. IFS= is required to avoid trimming leading/trailing whitespace, and -r is needed to avoid backslash processing. In fact, $'\0' is equivalent to '' so we could also write it like this:

# Bash
unset a i
while IFS= read -r -d '' file; do
  a[i++]="$file"
done < <(find /tmp -type f -print0)

So, why doesn't this work?

# DOES NOT WORK
unset a i
find /tmp -type f -print0 | while IFS= read -r -d '' file; do
  a[i++]="$file"
done

Because of the pipeline, the entire while loop is executed in a SubShell and therefore the array assignments will be lost after the loop terminates. (For more details about this, see FAQ #24.)


CategoryShell

BashFAQ/020 (last edited 2016-03-06 16:39:47 by GreyCat)