exa
fish-shell
Our great sponsors
exa | fish-shell | |
---|---|---|
129 | 320 | |
23,238 | 24,456 | |
- | 1.5% | |
3.2 | 9.9 | |
9 days ago | 5 days ago | |
Rust | 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.
exa
- Exa Is Deprecated
-
macOS Command-Line Tools You Might Not Know About
Some of us don't want all of GNU's utilities; just on an as-needed basis. They're not as needed as they once were.
Many of these utilities have been rewritten in Rust and have more modern features.
For example, instead of ls, I use exa [1]. Or ripgrep [2] instead of grep.
-
List of apps I use every day - Version 2023
fish: A very fast shell with various customization options to streamline daily commands. I discovered it through this post by @caarlos0, where he provides more details about performance and the differences between fish and zsh. Additionally, I use some CLI utilities like delta, exa, and ripgrep. Here's my dotfiles for fish.
-
Ls with icons
Hi! I use this: https://the.exa.website, and the package to this: https://archlinux.org/packages/extra/x86_64/exa/
-
Everything I Installed on My New Mac
I still use exa for listing files in the terminal. It's a modern replacement for ls with a lot of useful features. With icons, colors, and git integration, it makes listing files much nicer.
-
Top Productivity CLI Tools I Use on Linux
5. Exa
-
Use colorls and font-awesome to add colors and icons to your ls output
There's also exa
- ls is bloat
- Quick File Sorter: An open source tool for sorting your files on Linux
-
What kind of applications are missing from the Linux ecosystem?
Yeah, I see what you mean, perhaps exa could implement this, in case they don't already.
fish-shell
- Oh My Zsh
-
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
> 1. It's amazing that they're doing this as a gradual C++ to Rust rewrite, while keeping it working end-to-end, if I understand correctly.
Seems to me they're not doing it gradually at all.
> Another thing:
> We plan on not doing any partial-rust release.
> That means we would be doing e.g. fish 4.0 as fully rust and zero C++, and I think, contrary to what we usually do that warrants a beta. (Ordinarily we've stopped doing betas and release candidates because they simply don't get any testing).
> We also still want to do a 3.7.0 in-between release that is still purely C++, so we have a better jumping off point for platforms that can't handle the rust version. It would be 3.6.1 with some neat changes backported.
https://github.com/fish-shell/fish-shell/discussions/10123#d...
It has nothing to do with Windows. fish doesn't support Windows. Their use of wchar_t is the glibc wchar_t (wchar_t is not Microsoft-specific) which is a 32-bit type and stores UTF-32-encoded codepoints. The Rust type they're using is also the same ( https://github.com/fish-shell/fish-shell/blob/master/doc_int... ).
More on the motivation behind the rewrite.
https://github.com/fish-shell/fish-shell/pull/9512#issuecomm...
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.
What are some alternatives?
lsd - The next gen ls command
powerlevel10k - A Zsh theme
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
nushell - A new type of shell
colorls - A Ruby gem that beautifies the terminal's ls command, with color and font-awesome icons. :tada:
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!
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