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.

Universal configuration monitoring and system of record for IT.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags





Get each users commit amount

Terminal - Get each users commit amount
svn log 2>&1 | egrep '^r[0-9]+' | cut -d "|" -f2 | sort | uniq -c
2010-09-06 15:13:48
User: cicatriz
Functions: cut egrep sort uniq
Get each users commit amount


There are 5 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Heh, neat, you could also do a svn blame count, to see how many lines were changed by each user.

Here's the command for a single file:

svn blame ANY_FILENAME 2>&1 | awk '{print $2}' | sort | uniq -c

...or if you have a lot of free time on your hands, and want to do a svn blame count on all the files in the current directory branch:

svn list -R | sed '/\/$/ d' | xargs echo | xargs svn blame | awk '{print $2}' | sort | uniq -c

...removing "-R" from the previous command will just process the current directory, and will not delve into any subdirs

Comment by ArtBIT 265 weeks and 2 days ago

Thanks ArtBIT, that's really useful.

Comment by cicatriz 265 weeks ago

Your point of view

You must be signed in to comment.