mcfly VS zsh-histdb

It is a custom pretrained NN with very few nodes, the full source code is here: https://github.com/cantino/mcfly/blob/master/src/network.rs

I've had a great time using McFly (https://github.com/cantino/mcfly) for going through my command history. It prioritizes showing commands that were previously run in your current directory!

I end up installing mcfly (https://github.com/cantino/mcfly) in all my shells, and it works great in fish as well.

You should try https://github.com/cantino/mcfly, it replaces the Ctrl r bind for fuzzy-search-style patter matching, that you can see all the similar commands and then select the one you want, it has been on all my machines ever since I've learnd of it

There's also McFly which does the same thing.

https://github.com/cantino/mcfly

I've only used McFly and found it to be pretty great. My only complaint is the default search mode is SQL strings, so you have to use `%` for wildcards. I wish it was a more forgiving, less exact search.

Has anyone used both and could compare them?

If you like searching your Bash history with fzf, you're gonna love McFly: https://github.com/cantino/mcfly

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.