count how many times a string appears in a (source code) tree

grep -rc logged_in app/ | cut -d : -f 2 | awk '{sum+=$1} END {print sum}'
grep's -c outputs how may matches there are for a given file as "file:N", cut takes the N's and awk does the sum.
Sample Output
34

-2
By: terceiro
2009-07-15 14:16:44

1 Alternatives + Submit Alt

What Others Think

if you leave out the -c option of grep then you can get wc to do the counting for you: grep -r PATTERN app/ | wc -l because then grep returns one match per line.
bwoodacre · 462 weeks and 4 days ago
Strictly speaking this is how many *lines* upon which the string appears: echo foo foo |grep -c foo 1 You can use sed to add newlines after your input string to put each on a line by itself, to count them accurately: grep -r foo app/ | sed -e 's/foo/&\n/g' |grep -c foo
eichin · 462 weeks and 3 days ago
use $ awk -F\: '{sum+=$2} END {print sum}'
ioggstream · 462 weeks and 3 days ago
Good catch eichin. Although I think using wc is still a decent approximation. Another way if you're only searching for a single word is to turn all spaces into newlines: grep -r PATTERN app/ | tr ' ' '\n' | wc -l although as soon as you want to search for "Micheal Jackson" this approach fails and you have use eichin's approach.
bwoodacre · 462 weeks and 3 days ago
I missed the -o option on my first pass through the grep manpage. Indeed -o gets what we really want: grep -ro PATTERN . | wc -l
bwoodacre · 462 weeks and 3 days ago
ooh, I hadn't seen that before, nice. (As noted in the other thread, -o and -c don't play well together, but it's still a much nicer way to get non-overlapping matches, and it lets you avoid repeating the string too...)
eichin · 462 weeks and 2 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: