The same command is listed in my history again and again. How can I avoid this? I know it's possible via HISTCONTROL but I haven't found the right way.
- 698
- 81,947
-
I created a related question: http://askubuntu.com/questions/205520/history-list-without-timestamp-and-unique-the-results. Dups in the history is useful to see the context of a command. What you want to omit dups sometimes when you print the history. – justingordon Oct 24 '12 at 01:34
6 Answers
From the bash man page:
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 ofignoredupscauses lines matching the previous history entry to not be saved. A value ofignorebothis shorthand forignorespaceandignoredups. A value oferasedupscauses 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.
So put the following line in your ~/.bashrc:
export HISTCONTROL=ignoreboth:erasedups
- 59,344
-
Do you want me to add HISTCONTROL=ignoreboth in the bottom of ~/.bashrc? – karthick87 Dec 02 '10 at 20:11
-
1@karthick It doesn't matter where you put it, the bottom is fine though. – Isaiah Dec 02 '10 at 20:12
-
On my installation of Ubuntu 12.04 I had to make this modification in
~/.bash_loginMost of the time it would work if .bashrc is modified but that's not the case all the time. – ck- Jun 29 '12 at 11:06 -
3Don't forget to run these after you update your bash profile/rc files -
source ~/.bashrc && source ~/.bash_profile– Eric Kigathi Mar 23 '17 at 20:12
Stick this in your ~/.bashrc:
export HISTCONTROL=ignoredups
You could instead use ignoreboth. This it shorthand for both ignorespaces (commands starting with spaces) and ignoredups (duplicates).
I prefer ignoredups on its own as I find the default behaviour of ignoring commands with spaces at the front quite annoying when I copy a command off a website and it doesn't get saved because I accidentally copied in a space too.... But to each their own.
- 293,335
-
6Still duplicates exist..What may be the problem??http://imgur.com/fXeLQ.png – karthick87 Dec 10 '10 at 18:19
-
9@karthick87 quoted from another answer: A value of
ignoredupscauses lines matching the previous history entry to not be saved. It only removes consecutive identical lines. – A.L Feb 04 '15 at 09:28
Putting this in ~/.bashrc will apply @alvin's solution across different sessions as wlell
HISTCONTROL=ignoredups:erasedups
shopt -s histappend
PROMPT_COMMAND="history -n; history -w; history -c; history -r; $PROMPT_COMMAND"
-
Why does his use
export HISTCONTROLand yours doesn't? What's the difference? It's working for me without export, I'm just curious – felwithe Apr 07 '18 at 18:30 -
1Good question! I would also like to know the answer. In general
exportmakes the variable available to sub-processes. https://stackoverflow.com/q/1158091/552621 In the case ofHISTCONTROL,PROMPT_COMMAND, etc, these variables are used by the shell itself so maybe exporting them (to children processes) is not necessary. – Nour Wolf Apr 09 '18 at 15:23
Add the following to your ~/.bashrc:
export HISTCONTROL=ignoredups
To do this, you can use this command:
nano ~/.bashrc
- 60,611
To uniqely record every new command is tricky. First you need to add to
~/.profile or similar:
HISTCONTROL=erasedups
PROMPT_COMMAND='history -w'
Then you need to add to ~/.bash_logout:
history -a
history -w
- 1