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

Some discussion about cross pollination https://github.com/cantino/mcfly/issues/373

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

Find a replacement for Control-R (history search). mcfly or fzf will help immensely.

I use zsh-histdb which stores the history in SQLite with context. Then I have few different queries/ways to interact with it. For example I have a line completion (which also shows as grayed out text while I type) based on most frequently used commands with give prefix with additional weighting depending how close in the directory tree they were used.

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

The article briefly mentions atuin at the end. I've tried atuin but found it a little bit too heavyweight for me - instead I use zsh-histdb[0] (together with the fzf extension for it[1]) which allows you to easily answer this type of question - can highly recommend it.

0. https://github.com/larkery/zsh-histdb

1. https://github.com/m42e/zsh-histdb-fzf

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.

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).

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

Here is a zsh function I made for use with https://github.com/larkery/zsh-histdb to get the same effect, but only showing commands whose exit_status is 0:

jog() {

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.