4 ms·
I always thought I wanted an in-sync bash history but after a few days of trying I realised it actually slowed me down. I have multiple terminals open (with Ter
by dave1010uk 15y ago
I always thought I wanted an in-sync bash history but after a few days of trying I realised it actually slowed me down. I have multiple terminals open (with Terminator, most of the time) and different windows / tabs are for different projects or tasks. If I'm building / configuring a project in 1 window, suddenly having a few apt-gets or log tails interspersed is very unproductive.
- 6ren 15y agoYes, I found that too. It's convenient that up-arrow is context-specific. However, as a commenter on the blog said, the first suggestion avoids the "last logout wins" problem: shopt -s histappend
- kahawe 15y agohistappend is a must for me for any decent bash history usage; I like to set HISTCONTROL=ignoredups along with it to keep things clean and I increased HISTSIZE and HISTFILESIZE from the defaults. A good bash history can often save your behind when trying to reconstruct what you did or when you have to run that one magic command you last ran 5 months ago...
- naner 15y agoI am going to chime in with a similar sentiment. I also had bash configured like this for awhile when I realized it is not what I wanted. If you typically use different terminal windows for different tasks (e.g. terminal #1 for compiling, terminal #2 for manpages, terminal #3 for vim, etc.), this will just clutter up your history with items unrelated to what your are doing.
- Terretta 15y agoGranted. But then if tomorrow you do want a record of what you did in terminal 2 today? Multiple histories?