zsh-histdb
cheatsheet
| zsh-histdb | cheatsheet | |
|---|---|---|
| 16 | 4 | |
| 1,233 | 205 | |
| - | - | |
| 0.0 | 5.6 | |
| over 1 year ago | 9 days ago | |
| Shell | ||
| MIT License | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zsh-histdb
-
Which command did you run 1731 days ago?
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.
-
Save exit status of commands to history?
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.
-
Ask HN: Can I see your cheatsheet?
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
- RESH: Rich Enhanced Shell History
-
what are your top 5 most used shell commands?
(i use histdb for zsh, so i can easily do histdb-top).
-
After a reboot, history file maybe not parsing.
This error comes from https://github.com/larkery/zsh-histdb. Perhaps open an issue there?
-
Zsh Plugins Commit TOP
histdb 🥇 🚶♂️ ⏳ - Stores your history in an SQLite database. Can be integrated with zsh-autosuggestions.
- ZSH History Database
- Jog: Print the last 10 commands you ran in the current directory
-
What's a small Linux program that you don't give much thought but makes your life a hundred times easier from time to time?
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.
cheatsheet
-
Ask HN: Share a shell script you like
I have quite a few, my personal collection of shell scripts: https://github.com/fastily/autobots
I also curate a shell command cheatsheet: https://github.com/fastily/cheatsheet
- Can I see your cheatsheet?
- Ask HN: Can I see your cheatsheet?
What are some alternatives?
fzf - :cherry_blossom: A command-line fuzzy finder
cheat - cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind *nix system administrators of options for commands that they use frequently, but not frequently enough to remember.
atuin - ✨ Magical shell history
dotfiles
mcfly - Fly through your shell history. Great Scott!
learn_gnuawk - Example based guide to mastering GNU awk
rofi - Rofi: A window switcher, application launcher and dmenu replacement
tldr - 📚 Collaborative cheatsheets for console commands
navi - An interactive cheatsheet tool for the command-line
cheatsheets - Cheatsheets for web development - devhints.io
zsh-syntax-highlighting - Fish shell like syntax highlighting for Zsh.
dotfiles - My configuration files