AoC21
fish-shell
Our great sponsors
| AoC21 | fish-shell | |
|---|---|---|
| 1 | 320 | |
| 0 | 24,551 | |
| - | 1.9% | |
| 5.9 | 9.9 | |
| over 2 years ago | 2 days ago | |
| R | Rust | |
| - | 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.
AoC21
-
-π- 2021 Day 3 Solutions -π-
Bundled as a package
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?
Advent_of_Code_in_Pascal - My solutions to the Advent of Code, in Free Pascal
powerlevel10k - A Zsh theme
starship - βποΈ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
nushell - A new type of shell
oh-my-fish - The Fish Shell Framework
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
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.
oil - Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!
exa - A modern replacement for βlsβ.
oh-my-bash - A delightful community-driven framework for managing your bash configuration, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
kube-ps1 - Kubernetes prompt info for bash and zsh
fzf - :cherry_blossom: A command-line fuzzy finder