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.

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



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Check command history, but avoid running it

Terminal - Check command history, but avoid running it
2009-02-05 21:39:39
User: jonty
Check command history, but avoid running it

!whatever will search your command history and execute the first command that matches 'whatever'. If you don't feel safe doing this put :p on the end to print without executing. Recommended when running as superuser.


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

not working on my ubuntu machine or mac.

Comment by cowholio4 402 weeks and 6 days ago

Pressing +r then start typing the command will show you live updates of the history as you type. You can also use the up and down arrows to find the one your looking for.

Comment by pkkid 402 weeks and 6 days ago

@cowholio4: i got it working with both ubuntu and os x; you did not actually type in


did you?

Comment by p3k 402 weeks and 6 days ago

Works on Opensuse 11, very cool!

Comment by Williebee 402 weeks and 4 days ago

looklike it works, but may be batter to cat .bash_history?

or I`d just not understand the true meaning of this thing

Comment by GreyCardinal 402 weeks and 3 days ago

Oh! understood!

ubuntu 8.10 -works

debian etch - no -:(

Comment by GreyCardinal 402 weeks and 1 day ago


hahah.... thanks.

Still i prefer control + r

Comment by cowholio4 401 weeks and 3 days ago

I can only think that the :p means "just kidding about re-executing it" :)

Comment by Buzzcp 393 weeks and 3 days ago

ctrl+r works better and everywhere.

Comment by oringo 390 weeks and 2 days ago

... or you could just set histverify ("shopt -s histverify") and be done.

Comment by akg240 373 weeks ago

On ubuntu also:

history|grep whatever

That will show every time in your history file the command has been called rather than just the last time.

Comment by magikid 355 weeks ago

Agree with C-r

Comment by Erus 345 weeks and 6 days ago

use bash lusers! pkkid is right!

Comment by buzzy 339 weeks and 2 days ago

To those who say Ctrl-R works everwhere, try running Ctrl-R on csh/tcsh, or ksh, Ctrl-R only works on bash and Z shell. While !search:p works on many more, also it is more continent to type a simple command in than to use a shell feature, as you can use it in a string of commands.

Comment by Chartreuse 337 weeks and 4 days ago

function hg(){ history | grep $1; }

Then "hg command" will print all previous commands

Comment by quincymd 333 weeks and 2 days ago

it works fine like this:

1. type

echo hello

then you have it in your history. now you can type:


and you get "echo hello" in your commandline with the cursor at the end, so you can edit it before you commit it or you press ^C to cancel

very useful!

Comment by rubo77 314 weeks and 1 day ago

Your point of view

You must be signed in to comment.