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

disable history for current shell session

Terminal - disable history for current shell session
2009-05-20 14:46:18
User: syssyphus
Functions: unset
disable history for current shell session

this will cause any commands that you have executed in the current shell session to not be written in your bash_history file upon logout


There are 17 alternatives - vote for the best!

Terminal - Alternatives
2010-11-15 09:16:11
User: Delian
Functions: unset

Unsetting HISTFILE avoid getting current session history list saved.

history -c
ssh [email protected] "> ~/.bash_history"
2012-07-09 14:29:22
User: maxadamo
Functions: ssh

Only from a remote machine:

Only access to the server will be logged, but not the command.

The same way, you can run any command without loggin it to history.

ssh [email protected] will be registered in the history as well, and it's not usable.


Know a better way?

If you can do better, submit your command here.

What others think

to disable just one command type a space or two before it:

Comment by sudopeople 388 weeks and 1 day ago

@sudopeople I am not sure this is turned on in all shells. Doing some googling on bash says that setting the HISTIGNORE environment variable puts this into practice:

export HISTIGNORE="&:[ ]*:exit"

this would not add duplicate commands, those that begin with any amount of whitespace, and all 'exit' commands.

Comment by bwoodacre 388 weeks and 1 day ago


it's the same

Comment by xkill 388 weeks and 1 day ago

it's the same

Comment by xkill 388 weeks and 1 day ago

Your point of view

You must be signed in to comment.