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/
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.
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
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:
There are 5 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
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 -lusing xargs makes the command complete in 1 second:
find . -type f | xargs cat | wc -lAnytime you find yourself using a loop with find, there's a possibility that xargs could be helpful and a lot faster.
awesome, xargs version is definitely faster and lot better
thanks
no need to use cat, IMHO. below should suffice:
find . -type f | xargs wc -lSorry 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 -lYou see, if you use the \;, that would be the same as doing
(cat file1; cat file2; cat file3 ... ) | wc -lbut with the +, it's the same as doing
cat file1 file2 file3 ... | wc -lThat gets more to the real point of cat (concatenate, not print).