mcfly
zsh-histdb
Our great sponsors
mcfly | zsh-histdb | |
---|---|---|
49 | 16 | |
6,520 | 1,233 | |
- | - | |
7.2 | 0.0 | |
20 days ago | over 1 year ago | |
Rust | Shell | |
MIT License | MIT License |
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.
mcfly
-
Fly through your shell history
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
-
Cdpath: Easily Navigate Directories in the Terminal
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!
-
fish-shell: the user-friendly command-line shell
I end up installing mcfly (https://github.com/cantino/mcfly) in all my shells, and it works great in fish as well.
-
Linux terminal user
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
-
Atuin replaces your existing shell history with a SQLite database
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?
-
Fulfilling a reader's request for my “dot files”
If you like searching your Bash history with fzf, you're gonna love McFly: https://github.com/cantino/mcfly
- Happens too often
-
Advice to be more efficient with the terminal?
Find a replacement for Control-R (history search). mcfly or fzf will help immensely.
zsh-histdb
-
Which command did you run 1731 days ago?
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.
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.
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.
-
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.
- 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).
-
Zsh Plugins Commit TOP
histdb 🥇 🚶♂️ ⏳ - Stores your history in an SQLite database. Can be integrated with zsh-autosuggestions.
-
Jog: Print the last 10 commands you ran in the current directory
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() {
-
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.
What are some alternatives?
fzf - :cherry_blossom: A command-line fuzzy finder
atuin - ✨ Magical shell history
antigen - The plugin manager for zsh.
modern-unix - A collection of modern/faster/saner alternatives to common unix commands.
zoxide - A smarter cd command. Supports all major shells.
rofi - Rofi: A window switcher, application launcher and dmenu replacement
navi - An interactive cheatsheet tool for the command-line
z - z - jump around
ht - Friendly and fast tool for sending HTTP requests
zsh-syntax-highlighting - Fish shell like syntax highlighting for Zsh.