unset HISTFILE

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

17
By: syssyphus
2009-05-20 14:46:18

9 Alternatives + Submit Alt

What Others Think

to disable just one command type a space or two before it: ls
sudopeople · 469 weeks and 4 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.
bwoodacre · 469 weeks and 3 days ago
HISTFILE=/dev/null it's the same
xkill · 469 weeks and 3 days ago
HISTFILE=/dev/null it's the same
xkill · 469 weeks and 3 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands



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: