# # Bash HISTCONTROL
APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

Bash HISTCONTROL

I've removed advertising from most of this site and will eventually clean up the few pages where it remains.

While not terribly expensive to maintain, this does cost me something. If I don't get enough donations to cover that expense, I will be shutting the site down in early 2020.

If you found something useful today, please consider a small donation.



Some material is very old and may be incorrect today

© May 2006 Anthony Lawrence

I happened to come across Linux Tips: take control of your bash_history. This explains that setting "export HISTCONTROL=ignoreboth" causes Bash not to store duplicate commands in history. For example, if you are checking "ps" waiting for some process to end:


ps -e | grep foo

and keep pressing up arrow every few seconds to repeat it, you'll end up with a long list of those in your history if this isn't set. If it is set, you get only the last.

Actually there's much more to this than that little post exlained.

First, there's actually several values HISTCONTROL can take. On newer bash, it can be set to "ignorespace", "ignoredups", "ignoreboth" or "erasedups". Bash 2.05 doesn't have "erasedups".

If you want manual control over history, set "ignorespace". Then remember to use a space to precede any command you don't want to remember in history. Bash ignores leading spaces, so "  ls" is as good as "ls", but with "ignorespace" set, "  ls" won't be saved.

The "ignoredups" setting ignores repeated lines. Typing "ls" twenty times in a row only ends up with one of them in history. However, typing "ls" and then "ps" and then "ls" again will store "ls" and "ps" every time - unless you have bash 3 and set "erasedups". If that's set, no duplicates get entered in bash history at all.

You can also control bash history with HISTIGNORE. For example, if I
"declare -x HISTIGNORE=ls:ps"
, neither "ls" or "ps" will appear in my history. To ignore all two character commands, use "declare -x HISTIGNORE='??'".

I don't like extra commands cluttering up my history file, so I use "ignoreboth". When available, I use "erasedups", but if you are using history as a record of commands rather than just for the convenience of repetition, you don't want that.

Date stamp

One thing I do sometimes want in my Bash history is a date stamp.

If the purpose is just to manually do this as the need strikes (for example to record the start and stop of various projects), you can simply type:

`date` (no ENTER)

and then ESC CTRL-e ENTER, which of course generates an error but does nonetheless stamp the history file. If you don't like the error, do:

echo `date` ESC CTRL-e ENTER


If you found something useful today, please consider a small donation.



Got something to add? Send me email.





(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

->
-> Bash HISTCONTROL

6 comments


Inexpensive and informative Apple related e-books:

Are Your Bits Flipped?

Take Control of Preview

Sierra: A Take Control Crash Course

Photos for Mac: A Take Control Crash Course

Take Control of High Sierra





More Articles by © Anthony Lawrence







Sun Jun 8 02:22:30 2008: 4325   anonymous


I am hoping that the following is just for example's sake, but if not, type "man watch" to learn about your new best friend- in this case the simplest version is: watch "ps -e | grep foo"

"if you are checking "ps" waiting for some process to end:
ps -e | grep foo
and keep pressing up arrow every few seconds to repeat it,"






Sun Jun 8 10:39:41 2008: 4326   TonyLawrence

gravatar
Yes, it was just for example, but keep in mind that bash runs on lots of systems that do NOT have "watch". or anything like it.

Old Unix folk like me would be unlikely to use it anyway. Out of long habit, we'd write

while :
ps -e | grep foo
sleep 2
done

or whatever. So "watch" will never be our new best friend :-)







Mon Jun 9 01:18:00 2008: 4327   BigDumbDinosaur


Hey! Watch it with the "old UNIX folks" stuff. I resemble that remark!



Thu Apr 7 15:33:29 2011: 9434   Brade

gravatar


Thanks for the tips--I've seen similar advice from other pages on the web, including the one you linked. The problem is that, on my system, once the bash session ends, the duplicates reappear the next time a session is opened.

The problem was described by a stackoverflow member here: (link)

This is the exact problem I'm having. No matter if I use "ignoredups" or "erasedups" or both, The history updates correctly while my session is open, but once I close Terminal and reopen later, those duplicates are back. Extremely frustrating, to say the least. You wouldn't happen to know the reason for this? (Or can you duplicate the problem on a OS 10.6.7 machine?)



Thu Apr 7 16:44:12 2011: 9435   TonyLawrence

gravatar


Running OS X 10.6.7 with
HISTCONTROL=ignoreboth

I get no dupes.



Wed Nov 27 12:23:35 2013: 12372   anonymous

gravatar


echo $(date) ENTER

------------------------


Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us


Printer Friendly Version





The people I distrust most are those who want to improve our lives but have only one course of action in mind. (Frank Herbert)




Linux posts

Troubleshooting posts


This post tagged:

Linux

Shell

Unix



Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode