navi VS zsh-histdb

I've built something similar for myself (fzf+a bit of shell). But I realized that fzf's history view (with very long history buffer) works much better for my use case.

I still needed something to cover rare commands with dynamic arguments. That got covered by Navi: https://github.com/denisidoro/navi (takes more friction to add new command than with TBMK, but you get much more organized and easier to search tool).

navi repo add denisidoro/navi-tldr-pages Cloning https://github.com/denisidoro/navi-tldr-pages into /home//.local/share/navi/cheats/tmp... Cloning into '/home//.local/share/navi/cheats/tmp'... remote: Enumerating objects: 1841, done. remote: Counting objects: 100% (1841/1841), done. remote: Compressing objects: 100% (1756/1756), done. remote: Total 1841 (delta 83), reused 1839 (delta 83), pack-reused 0 Receiving objects: 100% (1841/1841), 504.71 KiB | 1.95 MiB/s, done. Resolving deltas: 100% (83/83), done. Hey, listen! navi encountered a problem. Do you think this is a bug? File an issue at https://github.com/denisidoro/navi. Caused by: 0: Failed to import cheatsheets from `denisidoro/navi-tldr-pages` 1: Failed to get cheatsheet files from finder 2: Failed to pass data to finder 3: Unable to prompt cheats to import 4: Broken pipe (os error 32)

Similar projects (in a way): navi

I think navi is a better alternative. You can create custom cheats too.

navi might help you with that

I like using navi, but idk if you want something that runs in the terminal.

There's also a cli program called tealdeer that does this kind of thing and uses a local cache. And there's a fuzzy search interactive cli cheatsheet program called navi that's also pretty cool (and you can write your own cheatsheets).

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.