对我来说，听起来像是shell脚本的工作:

for file in 'find -name *.xml'
do
   grep 'hello' file
done

或者类似的东西

我使用的方法是这样的:

find . -name <filename> -print0 | xargs -0 cat | grep <word2search4>

"find"的"-print0"参数和"xargs"的"-0"参数需要正确处理文件路径/名称中的空白。

在bash中，以下代码是合适的:

find /dir -type f -print0 | xargs -0i cat {} | grep whatever

这将找到/dir目录下的所有文件，并安全地将文件名输送到xargs中，xargs将安全地驱动grep。

如果你在/dir目录下有成千上万的文件，跳过xargs不是一个好主意;Cat将由于参数列表长度过大而中断。Xargs会帮你处理的。

-print0参数用于查找与xargs的-0参数相匹配，以正确处理带有空格的文件名。xargs的-i参数允许您在cat命令行中插入所需的文件名。括号被从find导入cat命令的文件名所取代。

Piping to another process (although this won't accomplish what you said you are trying to do): command1 | command2 This will send the output of command1 as the input of command2. -exec on a find (this will do what you want to do, but it's specific to find): find . -name '*.foo' -exec cat {} \; Everything between find and -exec are the find predicates you were already using. {} will substitute the particular file you found into the command (cat {} in this case); the \; is to end the -exec command. Send output of one process as command line arguments to another process: command2 `command1` For example: cat `find . -name '*.foo' -print` Note these are backquotes not regular quotes (they are under the tilde ~ on my keyboard). This will send the output of command1 into command2 as command line arguments. It's called command substitution. Note that file names containing spaces (newlines, etc) will be broken into separate arguments, though.

下面是我找到包含一些我感兴趣的内容的文件名的方法，只是一个简单的bash行，很好地处理文件名中的空格:

find . -name \*.xml | while read i; do grep '<?xml' "$i" >/dev/null; [ $? == 0 ] && echo $i; done

有几种方法可以将find命令返回的文件列表传递给cat命令，但从技术上讲，并非所有方法都使用管道，也没有一种方法实际上直接通过管道传递给cat。

The simplest is to use backticks (`): cat `find [whatever]` This takes the output of find and effectively places it on the command line of cat. This doesn't work well if find has too much output (more than can fit on a command-line) or if the output has special characters (like spaces). In some shells, including bash, one can use $() instead of backticks : cat $(find [whatever]) This is less portable, but is nestable. Aside from that, it has pretty much the same caveats as backticks. Because running other commands on what was found is a common use for find, find has an -exec action which executes a command for each file it finds: find [whatever] -exec cat {} \; The {} is a placeholder for the filename, and the \; marks the end of the command (It's possible to have other actions after -exec.) This will run cat once for every single file rather than running a single instance of cat passing it multiple filenames which can be inefficient and might not have the behavior you want for some commands (though it's fine for cat). The syntax is also a awkward to type -- you need to escape the semicolon because semicolon is special to the shell! Some versions of find (most notably the GNU version) let you replace ; with + to use -exec's append mode to run fewer instances of cat: find [whatever] -exec cat {} + This will pass multiple filenames to each invocation of cat, which can be more efficient. Note that this is not guaranteed to use a single invocation, however. If the command line would be too long then the arguments are spread across multiple invocations of cat. For cat this is probably not a big deal, but for some other commands this may change the behavior in undesirable ways. On Linux systems, the command line length limit is quite large, so splitting into multiple invocations is quite rare compared to some other OSes. The classic/portable approach is to use xargs: find [whatever] | xargs cat xargs runs the command specified (cat, in this case), and adds arguments based on what it reads from stdin. Just like -exec with +, this will break up the command-line if necessary. That is, if find produces too much output, it'll run cat multiple times. As mentioned in the section about -exec earlier, there are some commands where this splitting may result in different behavior. Note that using xargs like this has issues with spaces in filenames, as xargs just uses whitespace as a delimiter. The most robust, portable, and efficient method also uses xargs: find [whatever] -print0 | xargs -0 cat The -print0 flag tells find to use \0 (null character) delimiters between filenames, and the -0 flag tells xargs to expect these \0 delimiters. This has pretty much identical behavior to the -exec...+ approach, though is more portable (but unfortunately more verbose).