Better Bash History (2012)
sanctum.geek.nz
Better Bash History (2012)
1–10 of 85 posts
Re: Better Bash History (2012)
#2highly recommended for fellow ctrl-r addicts: https://github.com/junegunn/fzf
Re: Better Bash History (2012)
#3I set up my bash config to store history separately for each working directory (ie separate history files that I store under a $HOME/.bash_history_d directory) – so as I cd into a project directory, the history is populated with the commands that I've run within that directory.
I find this super-helpful to remind me of the context for projects – cd in, then up-arrow to whatever that command is I usually run to launch this server, grep this logfile, etc.
There are some downsides – sometimes I want to run the same command in directory X and also in subdirectory X/Y, but I love doing it this way.
Anyone else done something similar?
Re: Better Bash History (2012)
#4highly recommended for fellow ctrl-r addicts: https://github.com/junegunn/fzf
These ones are pretty good too:
Re: Better Bash History (2012)
#5can anyone please explain how BASH history on current Ubuntu, is different when logging in from different desktop machines, to the same login ? the dot-local directory or dot-gconf directory is part of this ? consternation..
Re: Better Bash History (2012)
#6I set up my bash config to store history separately for each working directory (ie separate history files that I store under a $HOME/.bash_history_d directory) – so as I cd into a project directory, the history is populated with the commands that I've run within that directory . I find this super-helpful to remind me of the context for projects – cd in, then up-arrow to whatever that command is I usually run to launc…
That's clever, I'd like that. Can you have another key to recall the global history, e.g. all the combined histories like you would normally see?
Re: Better Bash History (2012)
#7>By default, Bash only records a session to the `.bash_history` file on disk when the session terminates. This means that if you crash or your session terminates improperly, you lose the history up to that point.
I kept loosing my history consistently on my new installation because of this. I usually put my laptop to sleep, and pretty much never intentionally terminate my x-session except on kernel updates. But because its a cheapo laptop with a crappy battery, I would occasionally run out of battery when asleep or it just wont wake up.
Re: Better Bash History (2012)
#8Because this comes up every so often, I'll post this link again: I wrote a little widget that stores your bash history in a sqlite db. I haven't touched it in a while because I now rely on fzf and this doesn't integrate with it, though maybe I could make it do...
Re: Better Bash History (2012)
#9Bash's broken history is what finally got me to switch to Zsh. The history behavior you want is: 1. each line of history is appended incrementally, but 2. each shell session only has access to its own history unless you specifically reload the history into your session.
Every combination of history commands in bash didn't do the right thing[1], but Zsh's works as desired.
[1] eg. putting 'history -a' in PROMPT_COMMAND as the article recommends appends your session's entire history each time, IIRC.
Re: Better Bash History (2012)
#10Bash's broken history is what finally got me to switch to Zsh. The history behavior you want is: 1. each line of history is appended incrementally, but 2. each shell session only has access to its own history unless you specifically reload the history into your session. Every combination of history commands in bash didn't do the right thing[1], but Zsh's works as desired. [1] eg. putting 'history -a' in PROMPT_COMMAN…
See, what I want from my history is every command I have ever run, so that ctrl r can find anything I have done.