rgrep: recursive grep without .svn

alias rgrep="find . \( ! -name .svn -o -prune \) -type f -print0 | xargs -0 grep"
Only excludes .svn from filenames.
Sample Output
[nf@dev ~/css]$ rgrep sprites
./template.php:require "css_sprites.php";
./template.php: $abs_path.'/sprites/',
./template.php: 'sprites.css',
./template.php:include 'sprites.css';

By: nf
2009-02-05 11:23:23

1 Alternatives + Submit Alt

What Others Think

is this much different to this? http://www.commandlinefu.com/commands/view/59/search-through-files-ignoring-.svn
chrisdrew · 662 weeks and 2 days ago
pixelbeat · 662 weeks and 2 days ago
Grep can do this by itself: >> grep -r --exclude=*.svn search_query *
pkkid · 662 weeks and 2 days ago
Yes, it is similar to the above, although this is more correct because it only excludes files inside ".svn" directories, not just any file with ".svn" in the name. It also only uses one grep, where the other one needlessly uses grep twice. "Grep can do this by itself: >> grep -r --exclude=*.svn search_query" Wrong - try it. IMO (of course) this is the better one. But ultimately it's up to personal preference. I hope, for the reasons above, you will reconsider down-voting this entry.
nf · 662 weeks and 2 days ago
I had to change the command to >>find . \( ! -name .svn -o -prune \) | xargs grep for it to work
nitehawk · 640 weeks and 4 days ago
log0 · 639 weeks and 2 days ago
home health care columbus oh How can I get more infos about that products
yeoyeo · 48 weeks and 1 day ago
awesome. learned alot. keep posting more hair extensions halo
looneyhans · 34 weeks and 3 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: