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.

OpenID
or
Sign in Register

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

World cup college
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

2010-03-03 - Commandlinefu @ SXSW 2010
Am going to be at SXSW this year, in case you want to submit any CLI nuggets or suggestions to me in person. Ping me on the @codeinthehole Twitter account.
2009-09-12 - Email updates now available
You can now enable email updates to let you know each time you're command is commented on.
2009-07-11 - API and javascript blog widget now available
A simple API has been released, allowing commands to be retrieved in various formats. This also allows commands to be embedded on blogs/homepages.
2009-05-17 - Added duplicate suggestions to the new command form
When adding a new command, a quick background search is performed to make sure you're not duplicating a command already in the system.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Check command history, but avoid running it

Terminal - Check command history, but avoid running it
!whatever:p
2009-02-05 21:39:39
User: jonty
141
Up
Down
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.

Add to favourites | Report as malicious

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 57 weeks 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 57 weeks ago

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

!whatever:p

did you?

Comment by p3k 56 weeks and 6 days ago

Works on Opensuse 11, very cool!

Comment by Williebee 56 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 56 weeks and 3 days ago

Oh! understood!

ubuntu 8.10 -works

debian etch - no -:(

Comment by GreyCardinal 56 weeks and 2 days ago

@p3k

hahah.... thanks.

Still i prefer control + r

Comment by cowholio4 55 weeks and 4 days ago

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

Comment by Buzzcp 47 weeks and 3 days ago

ctrl+r works better and everywhere.

Comment by oringo 44 weeks and 3 days ago

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

Comment by akg240 27 weeks and 1 day 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 9 weeks and 1 day ago

Agree with C-r

Comment by Erus 11 hours ago

Your point of view

You must be signed in to comment.

Related sites and podcasts