95

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.

  • I created a related question: askubuntu.com/questions/205520/…. 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 1:34
109

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 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.

So put the following line in your ~/.bashrc:

export HISTCONTROL=ignoreboth:erasedups

  • Do you want me to add HISTCONTROL=ignoreboth in the bottom of ~/.bashrc? – karthick87 Dec 2 '10 at 20:11
  • 1
    @karthick It doesn't matter where you put it, the bottom is fine though. – Isaiah Dec 2 '10 at 20:12
  • On my installation of Ubuntu 12.04 I had to make this modification in ~/.bash_login Most 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
  • 2
    Don'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
20

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.

  • 2
    Still duplicates exist..What may be the problem??imgur.com/fXeLQ.png – karthick87 Dec 10 '10 at 18:19
  • 4
    @karthick87 quoted from another answer: A value of ignoredups causes lines matching the previous history entry to not be saved. It only removes consecutive identical lines. – A.L Feb 4 '15 at 9:28
8

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"

Source: Linux: Bash history: “ignoredups” and “erasedups” setting conflict with common history across sessions

  • Why does his use export HISTCONTROL and yours doesn't? What's the difference? It's working for me without export, I'm just curious – felwithe Apr 7 '18 at 18:30
  • Good question! I would also like to know the answer. In general export makes the variable available to sub-processes. stackoverflow.com/q/1158091/552621 In the case of HISTCONTROL, PROMPT_COMMAND, etc, these variables are used by the shell itself so maybe exporting them (to children processes) is not necessary. – Nour Chawich Apr 9 '18 at 15:23
4
export HISTCONTROL=erasedups
3

Add the following to your ~/.bashrc:

export HISTCONTROL=ignoredups

To do this, you can use this command:

nano ~/.bashrc
0

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

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.