Count lines of code across multiple file types, sorted by least amount of code to greatest

find . $ -iname '*.[ch]' -o -iname '*.php' -o -iname '*.pl' $ -exec wc -l {} \; | sort

Gives you a nice quick summary of how many lines each of your files is comprised of. (In this example, we just check .c, .h, .php and .pl). Since we just use wc -l to count, you'll just get a very rough estimate of how many lines of actual code there are. Use a more sophisticated algorithm instead if you need to.

Sample Output

18  ./binnum.c
22  ./helpers.h
35  ./gfx.h
112 ./lotto.pl     
144 ./ftp/upload.php

By: rkulla

2010-04-28 07:18:21

find wc find count code

2 Alternatives + Submit Alt

Count lines of code across multiple file types, sorted by least amount of code to greatest

The same as the other two alternatives, but now less forking! Instead of using '\;' to mark the end of an -exec command in GNU find, you can simply use '+' and it'll run the command only once with all the files as arguments. This has two benefits over the xargs version: it's easier to read and spaces in the filesnames work automatically (no -print0). [Oh, and there's one less fork, if you care about such things. But, then again, one is equal to zero for sufficiently large values of zero.] Show Sample Output
This is sample output - yours may be different.
```
  1105 ./intl/lock.h
  1336 ./intl/loadmsgcat.c
  1507 ./intl/localename.c
  1689 ./intl/dcigettext.c
  1961 ./intl/plural.c
  4677 ./intl/vasnprintf.c
 20716 total
```
5

find . $ -iname '*.[ch]' -o -iname '*.php' -o -iname '*.pl' $ -exec wc -l {} + | sort -n

hackerb9 · 2010-05-03 00:16:02 8
Count lines of code across multiple file types, sorted by least amount of code to greatest

find -exec is evil since it launches a process for each file. You get the total as a bonus. Also, without -n sort will sort by lexical order (that is 9 after 10).
This is sample output - yours may be different.
0

find . $ -iname '*.[ch]' -o -iname '*.php' -o -iname '*.pl' $ | xargs wc -l | sort -n

rbossy · 2010-04-30 12:21:28 9

What Others Think

rahimhh21 · 106 weeks and 1 day ago

Perfecthomepugs · 97 weeks and 3 days ago

pugpuppies95 · 59 weeks and 4 days ago

Clear, concise, and to the point! The author's ability to distill complex topics into easy words is commendable. I'll be recommending this blog to friends and family. shell pearl wholesaler

onenaturalpearl · 32 weeks and 6 days ago

yeneba6574 · 14 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

Similar Commands

count total number of lines of ruby code

count all the lines of code in a directory recursively

print code 3-up and syntax-highlighted for easy beach-time study

How many lines in your PHP project without comments

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:

» all commands
» commands with 3 up-votes (commandlinefu3)
» commands with 10 up-votes (commandlinefu10)