fast-syntax-highlightin VS fish-shell

Am i the only one who feels fish is not worth it despite of hype? Don't get me wrong. I think that fish is really good shell.

BUT...

After adding the following plugins to zsh(before you chime in, it's just adding these lines,not anything configuring much. also it auto bootstraps on new install), I found out that fish is no where near configured zsh.

1) https://github.com/zdharma-continuum/zinit (plugin manager)

2) https://github.com/zdharma-continuum/fast-syntax-highlightin...

3) https://github.com/zdharma-continuum/history-search-multi-wo...

4) https://github.com/zsh-users/zsh-autosuggestions

5) https://github.com/zsh-users/zsh-completions

6) https://github.com/Aloxaf/fzf-tab

7) any good shell prompt generator like https://github.com/romkatv/powerlevel10k

For example, I use fzf integration for tab completion. Fish's fzf integration is nowhere as good as that of zsh's. Also, posix compat and almost bash compat of zsh is plus.

I acknowledge that zsh isn't perfect shell either and I have tried and failed few times in past to switch to fish. If you provide me compelling reason/s to switch to fish, I am all ears.

Is anyone else mostly rolling with the zsh (not oh-my-zsh) defaults?

After so many years of using Bash I switched to zsh almost a year ago. I use the vanilla zsh set up with 2 plugins:

- https://github.com/zdharma-continuum/fast-syntax-highlightin... for very good and fast syntax highlighting

- https://github.com/zsh-users/zsh-autosuggestions for auto-suggestions

I don't use a plugin manager, instead I put together a ~20 line shell script[0] which handles either cloning or pulling plugins, then you can load them in your zshrc[1].

I haven't found the need for anything else and my whole dev environment is based on using tmux, terminal Vim, etc.. Basically I spend a lot of time there in my day to day.

[0] https://github.com/nickjj/dotfiles/blob/0076e508403c9981e393...

[1] https://github.com/nickjj/dotfiles/blob/0076e508403c9981e393...

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