4 ms·
Not parent poster, but I use zsh-histdb [0] to keep my history in an SQLite database. There is also Historian [1] for bash, and a bunch of other suggestions in
by aeontech 7y ago
Not parent poster, but I use zsh-histdb [0] to keep my history in an SQLite database.
There is also Historian [1] for bash, and a bunch of other suggestions in the discussion thread on it on HN [2]
[0]: https://github.com/larkery/zsh-histdb https://github.com/larkery/zsh-histdb
[1]: https://undertitled.com/2017/04/12/historian-because-please-stop-deleting-my-bash-history.html https://undertitled.com/2017/04/12/historian-because-please-...
[2]: https://news.ycombinator.com/item?id=14103688 https://news.ycombinator.com/item?id=14103688
- krzyk 7y ago> Not parent poster, but I use zsh-histdb [0] to keep my history in an SQLite database Why? A file is easier to grep (even if you have to pass `-a` to it after the file starts to be in the MBs, right now it is 7.4MB). I love having eternal command history in my zsh, and I wonder if I miss something out by not using SQLite for this.
- hashhar 7y agoI have a script that removes duplicates and HISTIGNORE set to ignore simple commands like cp, ls, mv, mkdir etc. In the past 5 years I've only executed around 20k unique commands using up around 900kb.