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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags



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 is 1 alternative - 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 user@localhost 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 305 weeks and 6 days 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 305 weeks and 6 days ago


it's the same

Comment by xkill 305 weeks and 6 days ago

it's the same

Comment by xkill 305 weeks and 6 days ago

Your point of view

You must be signed in to comment.