如果你可以假设文件名不包含换行符，你可以使用以下命令将find的输出读入Bash数组:

readarray -t x < <(find . -name '*.txt')

注意:

-t导致readarray删除换行符。 如果readarray在管道中，它将不起作用，因此需要进行进程替换。 readarray从Bash 4开始就可用了。

Bash 4.4及更高版本还支持-d参数来指定分隔符。使用空字符而不是换行符来分隔文件名也适用于文件名包含换行符的罕见情况:

readarray -d '' x < <(find . -name '*.txt' -print0)

Readarray也可以作为具有相同选项的mapfile调用。

参考:https://mywiki.wooledge.org/BashFAQ/005 # Loading_lines_from_a_file_or_stream

Filenames can include spaces and even control characters. Spaces are (default) delimiters for shell expansion in bash and as a result of that x=$(find . -name "*.txt") from the question is not recommended at all. If find gets a filename with spaces e.g. "the file.txt" you will get 2 separated strings for processing, if you process x in a loop. You can improve this by changing delimiter (bash IFS Variable) e.g. to \r\n, but filenames can include control characters - so this is not a (completely) safe method.

从我的角度来看，有两种推荐的(安全的)文件处理模式:

1. 用于循环和文件名扩展:

for file in ./*.txt; do
    [[ ! -e $file ]] && continue  # continue, if file does not exist
    # single filename is in $file
    echo "$file"
    # your code here
done

2. 使用find-read-while & process替换

while IFS= read -r -d '' file; do
    # single filename is in $file
    echo "$file"
    # your code here
done < <(find . -name "*.txt" -print0)

讲话

模式1:

bash returns the search pattern ("*.txt") if no matching file is found - so the extra line "continue, if file does not exist" is needed. see Bash Manual, Filename Expansion shell option nullglob can be used to avoid this extra line. "If the failglob shell option is set, and no matches are found, an error message is printed and the command is not executed." (from Bash Manual above) shell option globstar: "If set, the pattern ‘**’ used in a filename expansion context will match all files and zero or more directories and subdirectories. If the pattern is followed by a ‘/’, only directories and subdirectories match." see Bash Manual, Shopt Builtin other options for filename expansion: extglob, nocaseglob, dotglob & shell variable GLOBIGNORE

模式二:

filenames can contain blanks, tabs, spaces, newlines, ... to process filenames in a safe way, find with -print0 is used: filename is printed with all control characters & terminated with NUL. see also Gnu Findutils Manpage, Unsafe File Name Handling, safe File Name Handling, unusual characters in filenames. See David A. Wheeler below for detailed discussion of this topic. There are some possible patterns to process find results in a while loop. Others (kevin, David W.) have shown how to do this using pipes: files_found=1 find . -name "*.txt" -print0 | while IFS= read -r -d '' file; do # single filename in $file echo "$file" files_found=0 # not working example # your code here done [[ $files_found -eq 0 ]] && echo "files found" || echo "no files found" When you try this piece of code, you will see, that it does not work: files_found is always "true" & the code will always echo "no files found". Reason is: each command of a pipeline is executed in a separate subshell, so the changed variable inside the loop (separate subshell) does not change the variable in the main shell script. This is why I recommend using process substitution as the "better", more useful, more general pattern.See I set variables in a loop that's in a pipeline. Why do they disappear... (from Greg's Bash FAQ) for a detailed discussion on this topic.

其他参考资料和来源:

Gnu Bash手册，模式匹配 《Shell中的文件名和路径名:如何正确地做到这一点》，David A. Wheeler 格雷格的维基，你为什么不看带“for”的行 为什么不应该解析Greg的Wiki ls(1)的输出 Gnu Bash手册，进程替换

如果你可以假设文件名不包含换行符，你可以使用以下命令将find的输出读入Bash数组:

readarray -t x < <(find . -name '*.txt')

注意:

-t导致readarray删除换行符。 如果readarray在管道中，它将不起作用，因此需要进行进程替换。 readarray从Bash 4开始就可用了。

Bash 4.4及更高版本还支持-d参数来指定分隔符。使用空字符而不是换行符来分隔文件名也适用于文件名包含换行符的罕见情况:

readarray -d '' x < <(find . -name '*.txt' -print0)

Readarray也可以作为具有相同选项的mapfile调用。

参考:https://mywiki.wooledge.org/BashFAQ/005 # Loading_lines_from_a_file_or_stream

find . -name "*.txt"|while read fname; do
  echo "$fname"
done

注意:此方法和bmargulies所示的(第二个)方法在文件/文件夹名称中使用空白时是安全的。

为了在文件/文件夹名称中包含换行符，你必须使用find的-exec谓词，就像这样:

find . -name '*.txt' -exec echo "{}" \;

{}是找到的项的占位符，\;用于终止-exec谓词。

为了完整起见，让我添加另一个变体-你必须喜欢*nix的多功能性:

find . -name '*.txt' -print0|xargs -0 -n 1 echo

这将使用\0字符分隔打印项，据我所知，在任何文件系统的文件或文件夹名称中都不允许使用\0字符，因此应该涵盖所有基础。Xargs一个接一个地把它们捡起来，然后……

# Doesn't handle whitespace
for x in `find . -name "*.txt" -print`; do
  process_one $x
done

or

# Handles whitespace and newlines
find . -name "*.txt" -print0 | xargs -0 -n 1 process_one

TL;DR:如果你只是想知道最正确的答案，你可能想知道我的个人偏好(见本文底部):

# execute `process` once for each file
find . -name '*.txt' -exec process {} \;

如果有时间，请通读其余部分，了解几种不同的方法以及其中大多数方法的问题。

完整的答案是:

最好的方法取决于你想做什么，但这里有一些选择。只要子树中没有文件名中有空格的文件或文件夹，你就可以遍历这些文件:

for i in $x; do # Not recommended, will break on whitespace
    process "$i"
done

稍微好一点，去掉临时变量x:

for i in $(find -name \*.txt); do # Not recommended, will break on whitespace
    process "$i"
done

当你可以的时候，最好是glob。空白安全，对于当前目录中的文件:

for i in *.txt; do # Whitespace-safe but not recursive.
    process "$i"
done

通过启用globstar选项，你可以glob所有匹配的文件在这个目录和所有子目录:

# Make sure globstar is enabled
shopt -s globstar
for i in **/*.txt; do # Whitespace-safe and recursive
    process "$i"
done

在某些情况下，例如，如果文件名已经在文件中，你可能需要使用read:

# IFS= makes sure it doesn't trim leading and trailing whitespace
# -r prevents interpretation of \ escapes.
while IFS= read -r line; do # Whitespace-safe EXCEPT newlines
    process "$line"
done < filename

通过适当设置分隔符，Read可以安全地与find结合使用:

find . -name '*.txt' -print0 | 
    while IFS= read -r -d '' line; do 
        process "$line"
    done

对于更复杂的搜索，你可能会使用find，或者带-exec选项，或者带-print0 | xargs -0:

# execute `process` once for each file
find . -name \*.txt -exec process {} \;

# execute `process` once with all the files as arguments*:
find . -name \*.txt -exec process {} +

# using xargs*
find . -name \*.txt -print0 | xargs -0 process

# using xargs with arguments after each filename (implies one run per filename)
find . -name \*.txt -print0 | xargs -0 -I{} process {} argument

Find还可以在运行命令之前使用-execdir而不是-exec来CD到每个文件的目录，并且可以使用-ok而不是-exec(或-okdir而不是-execdir)来进行交互(在为每个文件运行命令之前提示)。

*:从技术上讲，find和xargs(默认情况下)都会在命令行中使用尽可能多的参数运行命令，次数与遍历所有文件所需的次数相同。在实践中，除非您有非常多的文件，否则这并不重要，如果您超过了长度，但需要在同一个命令行上全部使用它们，那么SOL就会找到不同的方法。