Stinkpot: SQLite-backed shell history

As indicated in https://tangled.org/oppi.li/stinkpot/blob/cdf87ffcd36e96f3d4... , this software (stinkpot) still uses Bash PROMPT_COMMAND as an entry point to copy new shell history entries to its database.

PROMPT_COMMAND has the following flaw: a command gets recorded as soon as it has finished. So command which never finish (e.g. because they run for a long time, and the user closes the terminal window, or reboots the system) never get recorded. Another flaw: the users starts a long-running command in terminal window 1, and immediately they want to start a variant of it in terminal window 2, but it's not available in the history.

FWIW I use atuin (https://atuin.sh/) and am reasonably happy with it, especially the infinite capacity & snapiness. Ignoring the sync features, I believe it's also sqlite backed when running in local-only mode.

Just enable perpetual bash history and install fzf. That will get you CTRL-R (and a lot of other niceties) out of the box.

<unrelated side note for the author>

I would never normally mention this, but I'm reading this repo on mobile & it seems Forgejo doesn't wrap .txt files on mobile. Any reason not to use .md for a new project in 2026?

For those of you on zsh, I have been a big fan of https://github.com/larkery/zsh-histdb

It is written entirely in shell script, with the only dependency being sqlite itself.

For me personally, while I like the history element, if I'm gathering/storing/searching everything, I'd love to also see the command output with the entered command, giving much better context.

Currently I tend to log all my ssh sessions out to text files and grep through the whole lot to find what I want, so a better version of that would be lovely, especially if it could automatically redact secrets or similar, as I'm aware thats a downside of the current setup.

I recently “fixed” my bash history since the default experience when using multiple terminals sucks.

https://dandavis.dev/the-bash-history-i-always-wanted.html

I also use fzf to search my history I believe you just need so source the right keybindings file to make ctrl+r use fzf.

A little curious but too lazy to find out, what's the difference between this and atuin vs fzf?

Also I do like the premise, recently stopped using atuin due to all the extra bells and whistles and just went back to fzf.

I have my own version that works without any ctrl-r https://github.com/AIex7/zsh-mouse-and-flex-search.

How do these compare to the fish builtin history search with dir awareness and completion menu? I found it quite an improvement to bash history handling but fish isn't POSIX compatible so sometimes you need to switch back and forth.

is there a particular reason why i'd want sqlite-backed shell history? i mean sure it works but why not a text file? (which i'd assume is somewhat faster because you can just append)

i guess you could say it's because you may want dates for each command but for that you can just use a CSV or TSV file no?

does it have to do with the searching?

Perfect! I wanted this without all the extras of atuin that I never use.

Would be interesting to have a non-interactive mode so you can ask your AI to look for a command too.. but I guess if it's sqlite underneath then it's already de facto possible (and the the cltr+r may be usable from harnesses too not sure)

I'm only interested in how it treats multiline commands in bash. It's the only thing that the default history doesn't do consistently (unless you make it replace \n with ;, which is just unuable). Otherwise, fzf + history works just fine.

Does it support just synching the db via nextcloud or similar? I'd prefer to stick to the Unix philosophy of one tool for one job instead of native cloud integration

created this gnome-extension to launch a gnome terminal with separate history files. bash script gt.sh [projname] launches a gnome-terminal with a history file in ~/.histories/projname

(https://github.com/appsmatics/gtsh-hist)

For me the killer feature of atuin is that it allows searching the history of commands executed from the current working directory. Typically I have 10,000 plus commands in history but only a few in the current directory and I tend to run the same complex commands from the same directory.

Does this automatically handle deduplication?

Great name

I wonder if the author is aware of McFly. That doesn't have all the features of Atuin that they say they don't want.

[flagged]

[flagged]

[dead]