Comments on: recursively grep only certain files http://adammonsen.com/post/301?utm_source=rss&utm_medium=rss&utm_campaign=recursively-grep-only-certain-files Sat, 31 Mar 2012 19:34:03 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: adamhttp://adammonsen.com/post/301/comment-page-1#comment-11479 adam Sun, 30 Sep 2007 22:45:21 +0000 http://adammonsen.com/post/301#comment-11479 While I'm at it, here's one way to recurse down selected directory paths, searching within files for an arbitrary pattern: <pre lang="bash"> #!/bin/bash find . -path '*.svn*' -prune -o -type f -print0 | xargs -0 grep --col "$1" </pre> This is of course a bash script wherein the first argument is the pattern to search for within the files. I've hardcoded it to skip any files including <code>'.svn'</code> in their full path. I guess I've also hardcoded where to start the search (the current directory). While I’m at it, here’s one way to recurse down selected directory paths, searching within files for an arbitrary pattern:

#!/bin/bash
find . -path '*.svn*' -prune -o -type f -print0 | xargs -0 grep --col "$1"

This is of course a bash script wherein the first argument is the pattern to search for within the files. I’ve hardcoded it to skip any files including '.svn' in their full path. I guess I’ve also hardcoded where to start the search (the current directory).

]]> By: adamhttp://adammonsen.com/post/301/comment-page-1#comment-11476 adam Wed, 26 Sep 2007 15:44:48 +0000 http://adammonsen.com/post/301#comment-11476 The first set of <code>egrep</code>s you provide are fine if you know the exact directory depth of the source files.<code>egrep</code> regex syntax is fine, I'm just more used to Perl-style regexes. The <code>-H</code> is necessary if find only passes one filename to xargs, but you're right, it would be fine to omit that.I agree the <code>grep</code> args <code>-r</code> paired with <code>--include</code> are conceptually the same as using find and piping to <code>xargs</code> and <code>grep</code>, but you're firing up three processes when only one is necessary. Also, the command line is a little shorter. :) The first set of egreps you provide are fine if you know the exact directory depth of the source files.

egrep regex syntax is fine, I’m just more used to Perl-style regexes. The -H is necessary if find only passes one filename to xargs, but you’re right, it would be fine to omit that.

I agree the grep args -r paired with --include are conceptually the same as using find and piping to xargs and grep, but you’re firing up three processes when only one is necessary. Also, the command line is a little shorter. :)

]]> By: jasonhttp://adammonsen.com/post/301/comment-page-1#comment-11473 jason Wed, 26 Sep 2007 05:52:48 +0000 http://adammonsen.com/post/301#comment-11473 what about: <pre lang="bash"> egrep '^#include +<rpc' */*.c egrep '^#include +<rpc' */*/*.c egrep '^#include +<rpc' */*/*/*.c egrep '^#include +<rpc' */*/*/*/*.c </pre>If you're in a hurry the command line substitution is pretty quick to add another splat slash to each one until you run out of directory depth.egrep has better support for regexes than plain 'ol grep does.<pre lang="bash"> find . -type f -name *.c -print0 |xargs -0 egrep '^#include +<rpc' </pre>I don't think you need the -P if you use egrep or the -H at all. I'm not sure what you're getting out of the -r as find is passing xargs fully qualified paths to files that you're searching. You can't descend to a subdirectory of a file.Maybe I'm missing something. etc... what about:

egrep '^#include +<rpc' */*.c
egrep '^#include +<rpc' */*/*.c
egrep '^#include +<rpc' */*/*/*.c
egrep '^#include +<rpc' */*/*/*/*.c

If you’re in a hurry the command line substitution is pretty quick to add another splat slash to each one until you run out of directory depth.

egrep has better support for regexes than plain ‘ol grep does.

find . -type f -name *.c -print0 |xargs -0 egrep '^#include +<rpc'

I don’t think you need the -P if you use egrep or the -H at all. I’m not sure what you’re getting out of the -r as find is passing xargs fully qualified paths to files that you’re searching. You can’t descend to a subdirectory of a file.

Maybe I’m missing something.
etc…

]]>