hydro VS fish-shell

This was already asked here. There's links in that discussion that may help. I use hydro and I've not noticed any issues. You might have luck trying another prompt and seeing if it's still an issue. Or, if you don't use any of the features of the automatic script injection, you might find the fix is simply changing this setting: "terminal.integrated.shellIntegration.enabled": false.

My prompt basically mimics Fish’s Hydro prompt. The left is a single line that has a truncated $PWD, my git branch, a single symbol for whether my git project dir is ‘dirty’, and a prompt symbol ($ in Bash, % in Zsh, # if I’m root). I use a transient right prompt in Zsh too with command execution times over 10s. Python venvs are the only other thing, but that happens automatically when I activate one. After using this for years, everything else now feels like clutter.

If you are interested in more in-depth profiling of your fish config, this command is helpful fish --profile-startup=$__fish_config_dir/fishprof.txt -c exit. You'll get detailed profile information in fishprof.txt. You will also probably find that starship is one of the slowest parts of your config. Hydro is a nice alternative if you like a full-featured prompt with speed in mind.

https://github.com/jorgebucaran/hydro is pretty minimal

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