Make a statistic about the lines of code

find . -type f -name "*.c" -exec cat {} \; | wc -l
use find to grep all .c files from the target directory, cat them into one stream, then piped to wc to count the lines
Sample Output
or some number else

By: foremire
2009-07-30 10:06:51

2 Alternatives + Submit Alt

What Others Think

To ignore whitespace only lines in the count, use grep which can both search and count: find . -type f -name "*.c" -exec cat {} + | grep -Evc '^[:space:]*$' This will also be faster due changing \; to +.
bwoodacre · 638 weeks and 3 days ago
Yeah, using + at the end of -exec is much faster than \; Thanks
foremire · 638 weeks and 2 days ago
Make a statistic about the lines of code. This lines of code is good at the time where we are waiting to check this law essay help code after implementing this code on different places. I never want to move on because we never stay even no one can force us to not try this here. We can do anything with these code lines.
Rogelson · 36 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: