shell VS zsh-histdb

If you were a fan of your favorite band before anyone else, you may also find https://github.com/abathur/shell-hag somewhat interesting.

I found it sad that there's so much overlapping effort (here, but in profile plug-ins broadly) so I also abstracted it's foundational shell glue out into its own module, https://github.com/abathur/shell swain.

I am slow-cooking them, for better and worse.

Totally agree with this. I use https://github.com/larkery/zsh-histdb slightly modified to work more smoothly for me. If I remember correctly, I tried Atuin but it messed up multi-line commands. Zsh-histdb handles them well.

Probably a bit overkill, but zsh-histdb stores a bunch of information about each command, including exit code, in an SQLite database. Perhaps you could draw some inspiration from that.

This the working directory of the command has been especially useful for me to get the context of what I did, not only the command itself.

[1] - https://github.com/larkery/zsh-histdb

(i use histdb for zsh, so i can easily do histdb-top).

This error comes from https://github.com/larkery/zsh-histdb. Perhaps open an issue there?

histdb 🥇 🚶‍♂️ ⏳ - Stores your history in an SQLite database. Can be integrated with zsh-autosuggestions.

zsh-histdb: store your command history in a sqlite database along with the exit status code and the directory the command was run in. Therefore no randomly losing portions of your command history based on which terminals you closed first or didn't close at all, and no getting weird garbage in your history from multi-line commands. I have a nearly complete history of every shell command I've typed since installing each of my machines.