zsh-abbr VS fish-shell

If you have trouble, open a GitHub issue https://github.com/olets/zsh-abbr/issues/new/choose

The abbreviations from Fish will expand the moment you hit space or execute the command. It's basically like an alias, but will expand. However this is not possible in Bash. Zsh itself does not support this, but there is an addon I am using for: https://github.com/olets/zsh-abbr

But you aren't limited to something OMZ specific. zsh-abbr is a manager for "abbreviations" (similar to auto-expanding aliases but with additional tools, and saving everything to a file which can be backed up). And there are zsh snippet managers… I haven't used any so can't speak to them; pet might be the most popular.

Something broke? Open an issue

Enhanced completion: Extend completion by syntax-aware completion, completion with quotes and parameter expansions in prefix texts, ambiguous candidate generation, etc. Also, menu-complete supports selection of candidates in menu (candidate list) by cursor keys, TAB and S-TAB. The feature auto-complete supports the automatic suggestion of completed texts as in fish and zsh-autosuggestions (with Bash 4.0+). The feature menu-filter integrates automatic filtering of candidates into menu completion (with Bash 4.0+). There are other functionalities such as dabbrev and sabbrev like zsh abbreviations or zsh-abbr.

I know. I have an addon for ZSH which mimics the Fish like abbreviations: https://github.com/olets/zsh-abbr

I am on ZSH and prefer abbreviations (with an addon to mimic Fish abbr), because the command will expand on typing and I change it before execution. Also it is then correctly logged as expanded version in the history. However, I also have a few aliases too:

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...

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/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

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.

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