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





Commands by unixmonkey8121 from sorted by
Terminal - Commands by unixmonkey8121 - 2 results
eh () { history -a ; vi ~/.bash_history ; history -r ; }
2011-03-23 18:00:20
Functions: vi

eh stands for Edit History


Frequently, I'll mistype a command, and then step back through my history and correct the command. As a result, both the correct and incorrect commands are in my history file. I wanted a simple way to remove the incorrect command so I don't run it by mistake.


When running this function, first the ~/bash_history file is updated, then you edit the file in vi, and then the saved history file is loaded back into memory for current usage.


while in vi, remember that `Shift-G` sends you to the bottom of the file, and `dd` removes a line.


this command is different than bash built-in `fc` because it does not run the command after editing.

sed -r 's_(/[^>]*?>)_\1\n_g' filename.html
2011-03-12 14:35:52
Functions: sed

Finds all the closing tags in a HTML document via non-greedy regex and adds a linefeed for easier reading/editing


sed -i.bak -r 's_(/[^>]*?>)_\1\n_g' filename.html


This will save a copy of filename.html as filename.html.bak and then add the linefeeds to the original file