Recursive Line Count

find ./ -not -type d | xargs wc -l | cut -c 1-8 | awk '{total += $1} END {print total}'

1
By: benschw
2009-04-01 15:14:15

1 Alternatives + Submit Alt

What Others Think

Good command, although some parts are unecessary. :-) Usage of 'cut' is superfluous, the $1 in the awk command will take the first (whitespace delimited) field on each line whether there are 1 or many fields per line. Usage of xargs is good to do batch invocations, but you can have find do that for you as well (see the find manpage). So the command could be: find ./ -not -type d -exec wc -l {} + | awk '{t+=$1} END {print t}'
bwoodacre · 537 weeks and 1 day ago
Suggestion of improvement: find * -type f -exec cat {} \;|wc -l
SlimG · 537 weeks and 1 day ago
I really like sloccount for this...
xSmurf · 536 weeks and 6 days ago
Actually it prints the wrong answer, cause `wc` will prints total in the end, so the result will be doubly. Problem occurs in both commends belong: find ./ -not -type d | xargs wc -l | cut -c 1-8 | awk '{total += $1} END {print total}' find ./ -not -type d -exec wc -l {} + | awk '{t+=$1} END {print t}' And follow up command can done it right: find * -type f -exec cat {} \;|wc -l But we have a faster one: find * -type f -not -name ".*" | wc -l We use `-not -name ".*"` for the reason we must omit hidden filed (which unnecessary). We can only show up total lines like this: find * -type f -not -name ".*" | wc -l | tail -1
Leechael · 477 weeks and 6 days ago
Sorry, I just submitted wrong commends, the right one is: find * -type f -not -name ".*" | xargs wc -l The one show up total only: find * -type f -not -name ".*" | xargs wc -l | tail -1 I had make sure they are correct this time. XDD
Leechael · 477 weeks and 6 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: