I use mainly Terminator, and it's usually opened with 3 split terminal windows. I also use Gnome terminal for various reasons.
I'm wondering how is bash history handled in this case as I sometimes miss previously issued commands when I run history
For example, my prompt shows current bash history line (\!
) and if I launch Terminator with 3 split terminal windows I get same history line (let's say 100) on all terminals. Which history will be saved?
Also launching Gnome Terminal after using Terminator I get line 100 at startup regardless all commands issued before in Terminator
The bash session that is saved is the one for the terminal that is closed the latest. If you want to save the commands for every session, you could use the trick explained here.
Anyway, you'll need to take into account that commands from different sessions will be mixed in your history file so it won't be so straightforward to read it later.
See also:
After multiple readings of
man bash
, I use separate history files for each shell. I did amkdir -m 0700 ~/.history
then addedto my
~/.bashrc
. Every now and then, I remember todu -sk .history
and clean it out. It's nice to have every command I've typed preserved for me.I just used the above to see what I'd been doing, of late:
cut -f1 "-d " .history/* | sort | uniq -c |sort -n -r |less
or
cut -f1-2 "-d " .history/* | sort | uniq -c |sort -n -r |less
(to include the 1st argument e.g.
sudo mount
in the sort chain).See also "keeping persistent history in bash" for another alternative. It rigs your prompt to send all commands ever typed into any terminal into a "persistent history" file (alongside what's usually done for the regular
.history
).To show
history
from all terminals:Add
export PROMPT_COMMAND='history -a; history -r'
to your .bashrc file.Source: http://northernmost.org/blog/flush-bash_history-after-each-command
History from all shell sessions is less useful than I hoped!
I enthusiastically set
PROMPT_COMMAND='history -a; history -r'
in the hopes that my history usage would be much better!Wow, was I disappointed.
Essentially, doing this makes up/dn arrow useless. Because now each history session is littered with commands from other sessions. And for me this loses the best feature of history.
What I really wanted
Occasionally, I wanted to essentially transfer my history from one terminal session to another session so I could easily recall commands from that session. And I can do this very selectively.
What I did
I set up a series of simple history manipulation aliases & I ignore these commands in the history:
I think of
hb
as history blend...the others are self-explanatory.Now when I want to copy my history from session A to session B, I can do this:
ha
- append session A history to history filehb
- append session B history to history file and then read the fileThis essentially preserves the history order for session B and adds session A history deeper in the list.
Super useful for me. Maybe helps you too!