This is actually a really interesting behavior and I confess I have greatly underestimated the question at the beginning. But first the facts:
1. What works
The functionality can be achieved in several ways, though each works a bit differently. Note that, in each case, to have the history "transferred" to another terminal (updated), one has to press Enter in the terminal, where he/she wants to retrieve the history.
This has two drawbacks:
- At login (opening a terminal), the last command from the history file is read twice into the current terminal's history buffer;
- The buffers of different terminals do not stay in sync with the history file.
(Yes, no need for shopt -s histappend and yes, it has to be history -c in the middle of PROMPT_COMMAND)
This version has also two important drawbacks:
- The history file has to be initialized. It has to contain at least one non-empty line (can be anything).
- The
history command can give false output - see below.
[Edit]
"And the winner is..."
This is as far as it gets. It is the only option to have both erasedups and common history working simultaneously.
This is probably the final solution to all your problems, Aahan.
2. Why does option 2 not seem to work (or: what really doesn't work as expected)?
As I mentioned, each of the above solutions works differently. But the most misleading interpretation of how the settings work comes from analysing the output of history command. In many cases, the command can give false output. Why? Because it is executed before the sequence of other history commands contained in the PROMPT_COMMAND! However, when using the second or third option, one can monitor the changes of .bash_history contents (using watch -n1 "tail -n20 .bash_history" for example) and see what the real history is.
3. Why option 3 is so complicated?
It all lies in the way erasedups works. As the bash manual states, "(...) erasedups causes all previous lines matching the current line to be removed from the history list before that line is saved". So this is really what the OP wanted (and not just, as I previously thought, to have no duplicates appearing in sequence). Here's why each of the history -. commands either has to or can not be in the PROMPT_COMMAND:
history -n has to be there before history -w to read from .bash_history the commands saved from any other terminal,
history -w has to be there in order to save the new history to the file after bash has checked if the command was a duplicate,
history -a must not be placed there instead of history -w, because it will add to the file any new command, regardless of whether it was checked as a duplicate.
history -c is also needed because it prevents trashing the history buffer after each command,
and finally, history -r is needed to restore the history buffer from file, thus finally making the history shared across terminal sessions.
Be aware that this solution will mess up the history order by putting all history from other terminals in front of the newest command entered in the current terminal. It also does not delete duplicate lines already in the history file unless you enter that command again.
As of bash-5.0-alpha, the history command now takes a range for the delete (-d) option. See rastafile's answer.
For older versions, workaround below.
You can use history -d offset builtin to delete a specific line from the current shell's history, or history -c to clear the whole history.
It's not really practical if you want to remove a range of lines, since it only takes one offset as an argument, but you could wrap it in a function with a loop.
rmhist() {
start=$1
end=$2
count=$(( end - start ))
while [ $count -ge 0 ] ; do
history -d $start
((count--))
done
}
Call it with rmhist first_line_to_delete last_line_to_delete. (Line numbers according to the output of history.)
(Use history -w to force a write to the history file.)
Best Answer
Yes. You can copy the old history file to a new install. You can also merge it with old / new.
HISTTIMEFORMATset the history file only holds commands.If it is set there is a timestamp preceded by a hash for each command:
Note however that if you issue e.g:
It is going to be saved as:
But
historyis going to show:Commands like:
are preserved as one if you set
shopt -s cmdhist.I use various but often something like:
shopt. (Use$ shoptto show current settings.)history.I also back up history files regularly and have some scripts and aliases to search history – even many years back in time. Sometimes I recall I did something similar to what I'm currently doing 1.5 years ago and can quickly look up in history.
As for timestamps I use two variants.
historyshows with timestamps and another show without by temporarily settingHISTTIMEFORMATto "".If timestamp is missing current time (approximately) is used. If timestamps are present history is sorted by times.
Thus:
.bash_history(Timestamps simplified)It is however reasonable to believe that a sorted history file is more effective (bash doesn't have to do any shuffling).
As for lookup Ctrl-R is often useful. For other things look at e.g. Commands For Manipulating The History, Event Designators, Some Miscellaneous Commands etc.