Count the lines of source code in directory, ignoring files in generated by svn

find . -name '*.java' -o -name '*.xml' | grep -v '\.svn' | xargs wc -l
There's nothing particularly novel about this combination of find, grep, and wc, I'm just putting it here in case I want it again.
Sample Output
123 ./src/java/com/company/app/service/
 42 ./test/java/com/company/app/service/
165 total

By: ewilson
2011-06-30 12:45:40

What Others Think

I can make the command a little shorter by using a regex for the filename matching. Then I'll make it longer again as I get rid of grep (it'll be quicker). find . -name .svn -prune -o -regex '.*\.\(java\|xml\)' -print | xargs wc -l
flatcap · 567 weeks and 3 days ago
Thanks, I didn't know about -prune. Yours is better, as the grep -v was wasteful. At the same time, I like that mine consists of smaller, easily understood pieces.
ewilson · 567 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? 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.


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: