grep_on_find_results
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
grep_on_find_results [2021/04/08 10:17] – raju | grep_on_find_results [2021/04/08 10:30] (current) – raju | ||
---|---|---|---|
Line 2: | Line 2: | ||
< | < | ||
find . -iname ' | find . -iname ' | ||
+ | </ | ||
+ | |||
+ | Another solution is to use xargs | ||
+ | < | ||
+ | find . -iname ' | ||
</ | </ | ||
Line 9: | Line 14: | ||
</ | </ | ||
- | Another solution | + | Notes: |
+ | |||
+ | Here is an excerpt from the man page of find (https:// | ||
< | < | ||
- | find . -iname '*.py' -print0 | xargs -0 grep something | + | -exec command {} + |
+ | This variant of the -exec action runs the specified | ||
+ | command on the selected files, but the command line is | ||
+ | built by appending each selected file name at the end; the | ||
+ | total number of invocations of the command will be much | ||
+ | less than the number of matched files. | ||
+ | is built in much the same way that xargs builds its | ||
+ | command lines. | ||
+ | within the command, and it must appear at the end, | ||
+ | immediately before the `+'; it needs to be escaped (with a | ||
+ | `\') or quoted to protect it from interpretation by the | ||
+ | shell. The command is executed in the starting directory. | ||
+ | If any invocation with the `+' | ||
+ | value as exit status, then find returns a non-zero exit | ||
+ | status. | ||
+ | cause an immediate exit, so some pending commands may not | ||
+ | be run at all. For this reason | ||
+ | command ... {} + -quit may not result in my-command | ||
+ | actually being run. This variant of -exec always returns | ||
+ | true. | ||
</ | </ | ||
grep_on_find_results.1617877043.txt.gz · Last modified: 2021/04/08 10:17 by raju