Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.


If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Count number of Line for all the files in a directory recursively

Terminal - Count number of Line for all the files in a directory recursively
for file in `find . -type f`; do cat $file; done | wc -l
2009-03-18 06:50:10
User: tejparkash
Functions: cat file wc
4
Count number of Line for all the files in a directory recursively

Alternatives

There are 4 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

This works. In a particular directory containing a source tree this takes 10 seconds for me after repeated runs.

Another way to do it without the bash for loop uses the -exec argument of find to invoke cat one for each file, and takes ~8 seconds:

find . -type f -exec cat {} \; | wc -l

using xargs makes the command complete in 1 second:

find . -type f | xargs cat | wc -l

Anytime you find yourself using a loop with find, there's a possibility that xargs could be helpful and a lot faster.

Comment by bwoodacre 284 weeks and 5 days ago

awesome, xargs version is definitely faster and lot better

thanks

Comment by tejparkash 284 weeks and 5 days ago

no need to use cat, IMHO. below should suffice:

find . -type f | xargs wc -l
Comment by alperyilmaz 284 weeks and 4 days ago

Sorry alperyilmaz, but your command doesn't work. It only tells you how many files there are, not how many lines are in them.

I like bwoodacre's first command, but I would make a slight change. I would do it as

find . -type f -exec cat {} + | wc -l

You see, if you use the \;, that would be the same as doing

(cat file1; cat file2; cat file3 ... ) | wc -l

but with the +, it's the same as doing

cat file1 file2 file3 ... | wc -l

That gets more to the real point of cat (concatenate, not print).

Comment by goodevilgenius 284 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts