blocks|key|952371|text|在GNU+find中，您可以使用-printf参数来实现此目的，例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|952372|find+/dir1+-type+f+-printf+"%25f\n"|code-block|syntax|javascript|952373|entityMap^0|5|4|G|7|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

In GNU <code>find</code> you can use <code>-printf</code> parameter for that, e.g.:

<pre><code>find /dir1 -type f -printf "%f\n"
</code></pre>

blocks|key|952487|text|如果你的find没有-printf选项，你也可以使用basename：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|952488|find+./dir1+-type+f+-exec+basename+{}+\;|code-block|syntax|javascript|952489|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If your find doesn't have a -printf option you can also use basename: 

<pre><code>find ./dir1 -type f -exec basename {} \;
</code></pre>

blocks|key|952430|text|如果您正在使用GNU，请查找|type|unstyled|depth|inlineStyleRanges|entityRanges|data|952431|find+.+-type+f+-printf+"%25f\n"|code-block|syntax|javascript|952432|或者您可以使用诸如Ruby(1.9%2B)之类的编程语言。|952433|$+ruby+-e+'Dir["**/*"].each{%7Cx%7C+puts+File.basename(x)}'|952434|如果您想要一个bash+(至少4个)解决方案|952435|shopt+-s+globstar
for+file+in+**;+do+echo+${file##*/};+done|952436|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

If you are using GNU find

<pre><code>find . -type f -printf "%f\n"
</code></pre>

Or you can use a programming language such as Ruby(1.9+)

<pre><code>$ ruby -e 'Dir["**/*"].each{|x| puts File.basename(x)}'
</code></pre>

If you fancy a bash (at least 4) solution

<pre><code>shopt -s globstar
for file in **; do echo ${file##*/}; done
</code></pre>

blocks|key|952636|text|如果您只想对文件名执行一些操作，那么使用basename可能会比较困难。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|952637|例如：|952638|find+~/clang%2Bllvm-3.3/bin/+-type+f+-exec+echo+basename+{}+\;+|code-block|syntax|javascript|952639|将只回显基名/my/found/path。如果我们想要在文件名上执行，这不是我们想要的。|952640|但是您可以对输出执行xargs操作。例如，要根据某个目录中的名称终止另一个目录中的文件：|952641|cd+dirIwantToRMin;
find+~/clang%2Bllvm-3.3/bin/+-type+f+-exec+basename+{}+\;+%7C+xargs+rm|952642|entityMap^0|K|8|0|0|0|6|E|0|A|5|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|J|7|15|8|@]|D|@]|E|$K|L]]|$1|S|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|T|$]]

If you want to run some action against the filename only, using <code>basename</code> can be tough.

For example this:

<pre><code>find ~/clang+llvm-3.3/bin/ -type f -exec echo basename {} \; 
</code></pre>

will just echo basename <code>/my/found/path</code>. Not what we want if we want to execute on the filename.

But you can then <code>xargs</code> the output. for example to kill the files in a dir based on names in another dir:

<pre><code>cd dirIwantToRMin;
find ~/clang+llvm-3.3/bin/ -type f -exec basename {} \; | xargs rm
</code></pre>

blocks|key|952728|text|在mac+(BSD+find)上使用：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|952729|find+/dir1+-type+f+-exec+basename+{}+\;|code-block|syntax|javascript|952730|entityMap^0|A|4|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

On mac (BSD <code>find</code>) use:

<pre><code>find /dir1 -type f -exec basename {} \;
</code></pre>

blocks|key|736809|text|正如其他人所指出的，您可以组合find和basename，但默认情况下，basename程序一次只在一个路径上运行，因此必须为每个路径启动一次可执行文件(使用find+...+-exec或find+...+%7C+xargs+-n+1)，这可能会很慢。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|736810|如果您在basename上使用-a选项，那么它可以在一次调用中接受多个文件名，这意味着您可以使用不带-n+1的xargs，将路径组合到数量少得多的basename调用中，这应该会更有效。|736811|示例：|736812|find+/dir1+-type+f+-print0+%7C+xargs+-0+basename+-a|code-block|syntax|javascript|736813|在这里，我包含了-print0和-0+(应该一起使用)，以便处理文件和目录名称中的空格。|736814|以下是xargs+basename+-a和xargs+-n1+basename版本之间的时序比较。(为了进行like-with-like比较，此处报告的计时是在初始虚拟运行之后进行的，因此它们都是在将文件元数据复制到I/O缓存之后进行的。)在这两种情况下，我都将输出通过管道传递给cksum，只是为了证明输出与所使用的方法无关。|736815|$+time+sh+-c+'find+/usr/lib+-type+f+-print0+%7C+xargs+-0+basename+-a+%7C+cksum'
2532163462+546663

real++++0m0.063s
user++++0m0.058s
sys+0m0.040s

$+time+sh+-c+'find+/usr/lib+-type+f+-print0+%7C+xargs+-0+-n+1+basename+%7C+cksum'+
2532163462+546663

real++++0m14.504s
user++++0m12.474s
sys+0m3.109s|736816|正如您所看到的，避免每次都启动basename确实要快得多。|736817|entityMap^0|F|4|K|8|10|8|27|E|2M|L|0|4|8|F|2|1E|4|1J|5|21|8|0|0|0|8|7|G|2|0|3|H|L|I|3W|5|0|0|F|8|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1K|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1L|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1M|8|@$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1R|8|@$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]]|D|@]|E|$]]|$1|S|3|T|5|L|7|1Y|8|@]|D|@]|E|$M|N]]|$1|U|3|V|5|6|7|1Z|8|@$9|20|A|21|B|C]]|D|@]|E|$]]|$1|W|3|-4|5|6|7|22|8|@]|D|@]|E|$]]]|X|$]]

As others have pointed out, you can combine <code>find</code> and <code>basename</code>, but by default the <code>basename</code> program will only operate on one path at a time, so the executable will have to be launched once for each path (using either <code>find ... -exec</code> or <code>find ... | xargs -n 1</code>), which may potentially be slow.

If you use the <code>-a</code> option on <code>basename</code>, then it can accept multiple filenames in a single invocation, which means that you can then use <code>xargs</code> without the <code>-n 1</code>, to group the paths together into a far smaller number of invocations of <code>basename</code>, which should be more efficient.

Example:

<pre><code>find /dir1 -type f -print0 | xargs -0 basename -a
</code></pre>

Here I've included the <code>-print0</code> and <code>-0</code> (which should be used together), in order to cope with any whitespace inside the names of files and directories.

Here is a timing comparison, between the <code>xargs basename -a</code> and <code>xargs -n1 basename</code> versions. (For sake of a like-with-like comparison, the timings reported here are after an initial dummy run, so that they are both done after the file metadata has already been copied to I/O cache.) I have piped the output to <code>cksum</code> in both cases, just to demonstrate that the output is independent of the method used.

<pre><code>$ time sh -c 'find /usr/lib -type f -print0 | xargs -0 basename -a | cksum'
2532163462 546663

real 0m0.063s
user 0m0.058s
sys 0m0.040s

$ time sh -c 'find /usr/lib -type f -print0 | xargs -0 -n 1 basename | cksum' 
2532163462 546663

real 0m14.504s
user 0m12.474s
sys 0m3.109s
</code></pre>

As you can see, it really is substantially faster to avoid launching <code>basename</code> every time.

blocks|key|952791|text|-exec和-execdir很慢，xargs是王道。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|952792|$+alias+f='time+find+/Applications+-name+"*.app"+-type+d+-maxdepth+5';+\
f+-exec+basename+{}+\;+%7C+wc+-l;+\
f+-execdir+echo+{}+\;+%7C+wc+-l;+\
f+-print0+%7C+xargs+-0+-n1+basename+%7C+wc+-l;+\
f+-print0+%7C+xargs+-0+-n1+-P+8+basename+%7C+wc+-l;+\
f+-print0+%7C+xargs+-0+basename+%7C+wc+-l

+++++139
++++0m01.17s+real+++++0m00.20s+user+++++0m00.93s+system
+++++139
++++0m01.16s+real+++++0m00.20s+user+++++0m00.92s+system
+++++139
++++0m01.05s+real+++++0m00.17s+user+++++0m00.85s+system
+++++139
++++0m00.93s+real+++++0m00.17s+user+++++0m00.85s+system
+++++139
++++0m00.88s+real+++++0m00.12s+user+++++0m00.75s+system|code-block|syntax|javascript|952793|xargs的并行性也很有帮助。|952794|有趣的是，如果没有-n1，我无法解释xargs的最后一个案例。它给出了正确的结果，而且是最快的¯\_(ツ)_/¯|952795|(basename只接受1个路径参数，但xargs将在没有-n1的情况下发送所有路径参数(实际上是5000个)。不能在linux和openbsd上工作，只能在macOS上工作...)|952796|来自linux系统的一些更大的数字，看看-execdir是如何提供帮助的，但仍然比并行xargs慢得多。|952797|$+alias+f='time+find+/usr/+-maxdepth+5+-type+d'
$+f+-exec+basename+{}+\;+%7C+wc+-l;+\
f+-execdir+echo+{}+\;+%7C+wc+-l;+\
f+-print0+%7C+xargs+-0+-n1+basename+%7C+wc+-l;+\
f+-print0+%7C+xargs+-0+-n1+-P+8+basename+%7C+wc+-l

2358
++++3.63s+real+++++0.10s+user+++++0.41s+system
2358
++++1.53s+real+++++0.05s+user+++++0.31s+system
2358
++++1.30s+real+++++0.03s+user+++++0.21s+system
2358
++++0.41s+real+++++0.03s+user+++++0.25s+system|952798|entityMap^0|0|5|6|8|H|5|0|0|0|5|0|9|3|I|5|1B|9|0|1|8|K|5|T|3|0|K|8|17|5|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|S|3|T|5|H|7|1Q|8|@]|D|@]|E|$I|J]]|$1|U|3|-4|5|6|7|1R|8|@]|D|@]|E|$]]]|V|$]]

<code>-exec</code> and <code>-execdir</code> are slow, <code>xargs</code> is king.

<pre class="lang-sh prettyprint-override"><code>$ alias f='time find /Applications -name "*.app" -type d -maxdepth 5'; \
f -exec basename {} \; | wc -l; \
f -execdir echo {} \; | wc -l; \
f -print0 | xargs -0 -n1 basename | wc -l; \
f -print0 | xargs -0 -n1 -P 8 basename | wc -l; \
f -print0 | xargs -0 basename | wc -l

 139
 0m01.17s real 0m00.20s user 0m00.93s system
 139
 0m01.16s real 0m00.20s user 0m00.92s system
 139
 0m01.05s real 0m00.17s user 0m00.85s system
 139
 0m00.93s real 0m00.17s user 0m00.85s system
 139
 0m00.88s real 0m00.12s user 0m00.75s system
</code></pre>

<code>xargs</code>'s parallelism also helps.

Funnily enough i cannot explain the last case of <code>xargs</code> without <code>-n1</code>.
It gives the correct result and it's the fastest <code>¯\_(ツ)_/¯</code>

(<code>basename</code> takes only 1 path argument but <code>xargs</code> will send them all (actually 5000) without <code>-n1</code>. does not work on linux and openbsd, only macOS...)

Some bigger numbers from a linux system to see how <code>-execdir</code> helps, but still much slower than a parallel <code>xargs</code>:

<pre><code>$ alias f='time find /usr/ -maxdepth 5 -type d'
$ f -exec basename {} \; | wc -l; \
f -execdir echo {} \; | wc -l; \
f -print0 | xargs -0 -n1 basename | wc -l; \
f -print0 | xargs -0 -n1 -P 8 basename | wc -l

2358
 3.63s real 0.10s user 0.41s system
2358
 1.53s real 0.05s user 0.31s system
2358
 1.30s real 0.03s user 0.21s system
2358
 0.41s real 0.03s user 0.25s system
</code></pre>

blocks|key|736747|text|老实说，basename和dirname解决方案更容易，但你也可以看看这个：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|736748|find+.+-type+f+%7C+grep+-oP+"[%5E/]*$"|code-block|syntax|javascript|736749|或|736750|find+.+-type+f+%7C+rev+%7C+cut+-d+'/'+-f1+%7C+rev|736751|736752|find+.+-type+f+%7C+sed+"s/.*\///"|736753|entityMap^0|4|8|D|7|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Z|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|O|3|L|5|6|7|11|8|@]|D|@]|E|$]]|$1|P|3|Q|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|R|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|S|$]]

Honestly <code>basename</code> and <code>dirname</code> solutions are easier, but you can also check this out :

<pre><code>find . -type f | grep -oP "[^/]*$"
</code></pre>

or

<pre><code>find . -type f | rev | cut -d '/' -f1 | rev
</code></pre>

or

<pre><code>find . -type f | sed "s/.*\///"
</code></pre>

blocks|key|952546|text|我找到了一个解决方案(在makandracards页面上)，它只给出最新的文件名：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|952547|ls+-1tr+*+%7C+tail+-1|code-block|syntax|javascript|952548|(感谢Arne+Hartherz)|952549|我把它用在cp上|offset|length|style|CODE|952550|cp+$(ls+-1tr+*+%7C+tail+-1)+/tmp/|952551|entityMap^0|0|0|0|5|2|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@$K|W|L|X|M|N]]|9|@]|A|$]]|$1|O|3|P|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I've found a solution (on makandracards page), that gives just the newest file name: 

<pre><code>ls -1tr * | tail -1
</code></pre>

(thanks goes to Arne Hartherz)

I used it for <code>cp</code>:

<pre><code>cp $(ls -1tr * | tail -1) /tmp/
</code></pre>

I'm using find to all files in directory, so I get a list of paths. However, I need only file names. i.e. I get <code>./dir1/dir2/file.txt</code> and I want to get <code>file.txt</code>

How to only get file name with Linux 'find'?

我使用find来查找目录中的所有文件，所以我得到了一个路径列表。但是，我只需要文件名。例如，我得到./dir1/dir2/file.txt，我想得到file.txt

问如何只获取带有Linux 'find‘的文件名？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何只获取带有Linux 'find‘的文件名？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何只获取带有Linux 'find‘的文件名？
EN