Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How do I prevent commands from showing up in Bash history?

Tags:

bash

Sometimes, when I run commands like rm -rf XYZ, I don't want this to be recorded in Bash history, because I might accidentally run the same command again by reverse-i-search. Is there a good way to prevent this from happening?

like image 858
Jeeyoung Kim Avatar asked Jun 25 '11 03:06

Jeeyoung Kim


People also ask

How do I turn off bash history?

How to permanently disable bash history using set command. Again add set +o history to the end of to a new /etc/profile. d/disable. history.

How do I edit bash history files?

In the Terminal just type open -e ~/. bash_history . This command will open the file with TextEdit, you can choose any other text editor, of course. Modify the file and save.

Should you clear bash history?

It is important to note that bash shell does not immediately flush history to the bash_history file. So, it is important to (1) flush the history to the file, and (2) clear the history, in all terminals.

Where is bash command history stored?

In Bash, your command history is stored in a file ( . bash_history ) in your home directory.


2 Answers

If you've set the HISTCONTROL environment variable to ignoreboth (which is usually set by default), commands with a leading space character will not be stored in the history (as well as duplicates).

For example:

$ HISTCONTROL=ignoreboth $ echo test1 $  echo test2 $ history | tail -n2  1015  echo test1  1016  history | tail -n2 

Here is what man bash says:

HISTCONTROL

A colon-separated list of values controlling how commands are saved on the history list. If the list of values includes ignorespace, lines which begin with a space character are not saved in the history list. A value of ignoredups causes lines matching the previous history entry to not be saved. A value of ignoreboth is shorthand for ignorespace and ignoredups. A value of erasedups causes all previous lines matching the current line to be removed from the history list before that line is saved. Any value not in the above list is ignored. If HISTCONTROL is unset, or does not include a valid value, all lines read by the shell parser are saved on the history list, subject to the value of HISTIGNORE. The second and subsequent lines of a multi-line compound command are not tested, and are added to the history regardless of the value of HISTCONTROL.

See also:

  • Why is bash not storing commands that start with spaces? at unix SE
  • Why does bash have a HISTCONTROL=ignorespace option? at unix SE
like image 157
kenorb Avatar answered Nov 03 '22 17:11

kenorb


In your .bashrc/.bash_profile/wherever you want, put export HISTIGNORE=' *'. Then just begin any command you want to ignore with one space.

$ ls  # goes in history $  ls # does not 
like image 31
rhdoenges Avatar answered Nov 03 '22 16:11

rhdoenges