zsh-histdb VS cheat

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.

Looks like bro pages is archived and they recommend https://github.com/tldr-pages/tldr or https://github.com/cheat/cheat

I tried eg and tldr, but I preferred cheat. Why, and why not. Cheat not only have nice examples, but let you improve them or create yours. I use the cli, not the curl.

Hey, the app I recommend shows you all the commands you need per app not just for macOS! Support for programming languages? Download this. For git, docker and neovim download this one.

cheat is also a useful one. Shows you a cheat sheet for the command you search.

are you sure autocompletion isn't enabled for cheat? You're maybe hitting this bug upstream.

Find something to automate or make easier and write a script for it. If you get stuck on a detail, read the man pages of the command you're using (man pages confuse you? try tldr or cheat). Then google it, there's a shitton of SO Q&A on bash. If you can't find it, find a bash channel on irc or discord and ask (they'll expect you've read the FAQ though). Keep notes. I wrote a script to read and edit notes for bash, in bash, and it taught me new things!

Definitely do. I created my own doc site using docusaurus where i stored a lot of info i use every once in a while. Things i use more often are available as aliases in the shell or zsh functions. There's also the handy dandy cli https://github.com/cheat/cheat that contains a lot of cheat sheets for common binaries.

cheat and howdoi

As a dev - It's a good (very good, in fact) alternative for man, tldr, cheat and zeal (and probably tens of other projects - sorry for not mentioning you) with a very pleasant interface - which was the point I think ;)