zsh-histdb
fd
zsh-histdb | fd | |
---|---|---|
16 | 172 | |
1,233 | 31,668 | |
- | - | |
0.0 | 8.8 | |
over 1 year ago | 5 days ago | |
Shell | Rust | |
MIT License | Apache License 2.0 |
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.
fd
-
Level Up Your Dev Workflow: Conquer Web Development with a Blazing Fast Neovim Setup (Part 1)
ripgrep: A super-fast file searcher. You can install it using your system's package manager (e.g., brew install ripgrep on macOS). fd: Another blazing-fast file finder. Installation instructions can be found here: https://github.com/sharkdp/fd
-
Hyperfine: A command-line benchmarking tool
hyperfine is such a great tool that it's one of the first I reach for when doing any sort of benchmarking.
I encourage anyone who's tried hyperfine and enjoyed it to also look at sharkdp's other utilities, they're all amazing in their own right with fd[1] being the one that perhaps get the most daily use for me and has totally replaced my use of find(1).
[1]: https://github.com/sharkdp/fd
-
Z – Jump Around
You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.
I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.
¹ https://github.com/sharkdp/fd
² https://github.com/junegunn/fzf
-
Unix as IDE: Introduction (2012)
Many (most?) of them have been overhauled with success. For find there is fd[1]. There's batcat, exa (ls), ripgrep, fzf, atuin (history), delta (diff) and many more.
Most are both backwards compatible and fresh and friendly. Your hardwon muscle memory still of good use. But there's sane flags and defaults too. It's faster, more colorful (if you wish), better integration with another (e.g. exa/eza or aware of git modifications). And, in my case, often features I never knew I needed (atuin sync!, ripgrep using gitignore).
1 https://github.com/sharkdp/fd
- Tell HN: My Favorite Tools
-
Potencializando Sua Experiência no Linux: Conheça as Ferramentas em Rust para um Desenvolvimento Eficiente
Descubra mais sobre o fd em: https://github.com/sharkdp/fd
-
Making Hard Things Easy
AFAIK there is a find replacement with sane defaults: https://github.com/sharkdp/fd , a lot of people I know love it.
However, I already have this in my muscle memory:
-
🐚🦀Comandos shell reescritos em Rust
fd
-
Oils 0.17.0 – YSH Is Becoming Real
> without zsh globs I have to remember find syntax
My "solution" to this is using https://github.com/sharkdp/fd (even when in zsh and having glob support). I'm not sure if using a tool that's not present by default would be suitable for your use cases, but if you're considering alternate shells, I suspect you might be
-
Bfs 3.0: The Fastest Find Yet
Nice to see other alternatives to find. I personally use fd (https://github.com/sharkdp/fd) a lot, as I find the UX much better. There is one thing that I think could be better, around the difference between "wanting to list all files that follow a certain pattern" and "wanting to find one or a few specific files". Technically, those are the same, but an issue I'll often run into is wanting to search something in dotfiles (for example the Go tools), use the unrestricted mode, and it'll find the few files I'm looking for, alongside hundreds of files coming from some cache/backup directory somewhere. This happens even more with rg, as it'll look through the files contents.
I'm not sure if this is me not using the tool how I should, me not using Linux how I should, me using the wrong tool for this job, something missing from the tool or something else entirely. I wonder if other people have this similar "double usage issue", and I'm interested in ways to avoid it.
What are some alternatives?
fzf - :cherry_blossom: A command-line fuzzy finder
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
atuin - ✨ Magical shell history
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore
mcfly - Fly through your shell history. Great Scott!
rofi - Rofi: A window switcher, application launcher and dmenu replacement
exa - A modern replacement for ‘ls’.
navi - An interactive cheatsheet tool for the command-line
skim - Fuzzy Finder in rust!
zsh-syntax-highlighting - Fish shell like syntax highlighting for Zsh.
vim-grepper - :space_invader: Helps you win at grep.