zsh-histdb
fish-shell
zsh-histdb | fish-shell | |
---|---|---|
16 | 320 | |
1,233 | 24,593 | |
- | 0.9% | |
0.0 | 9.9 | |
over 1 year ago | 5 days ago | |
Shell | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
fish-shell
-
FAQ on the xz-utils backdoor β via a project dev
Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.
https://github.com/fish-shell/fish-shell/releases/tag/3.7.1
https://github.com/fish-shell/fish-shell/issues/7772#issueco...
https://gitlab.archlinux.org/archlinux/packaging/packages/fi...
- Oh My Zsh
- Proposal for porting fish-shell from C++ to Rust
-
Converting the Kernel to C++
A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123
An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust
It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123
-
Day 5 - More or less...
We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.
-
Fish β Update on the Rust Port
They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.
[1] https://github.com/fish-shell/fish-shell/pull/9512
- Devuan γ’γγγ°γ¬γΌγ: 4 γγ 5 Daedalus γΈ
What are some alternatives?
fzf - :cherry_blossom: A command-line fuzzy finder
powerlevel10k - A Zsh theme
atuin - β¨ Magical shell history
starship - βποΈ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
mcfly - Fly through your shell history. Great Scott!
nushell - A new type of shell
rofi - Rofi: A window switcher, application launcher and dmenu replacement
oh-my-fish - The Fish Shell Framework
navi - An interactive cheatsheet tool for the command-line
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
zsh-syntax-highlighting - Fish shell like syntax highlighting for Zsh.
tokyonight.nvim - π A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.