tide VS fish-shell

Tide is as close to powerlevel10k as one can get in Fish.

https://github.com/IlanCosman/tide

tide theme

> The main inconvenience of fish is not even having to go into another shell for some tasks like virtual env activation, but wondering whether some command you just ran silently did something wrong because of shell incompatibility.

I have the impression that you just overlook all the rest of the things that can go wrong when using Bash, because you are simply used to it, you know it and you know how it will behave.

> Also, I wonder how fast is OMF compared to Starship?

Those are two total different projects that do not conflict at all. Personally, during my hypomania on Fish (yup), I didn't even use OMF, but added things manually and only those really needed, so that there was as little code to to maintain as possible. Fish does not have a huge number of scripts, plug-ins. If Starship is too slow for you, you might like tide. I found nothing more interesting, after which I returned to Starship anyway, but it's really fast.

https://github.com/IlanCosman/tide

Perhaps you don't need something faster than Starship, just to configure Fish in such a way that it cleans itself of garbage and runs asynchronously?

I'm using a custom terminal prompt. Mine is tide for fish shell but there are many others. A lot of people use starship, which works on every terminal

Agreed. I personally like Fisher (https://github.com/jorgebucaran/fisher) with this theme based on Powerlevel10k (https://github.com/IlanCosman/tide)

fixed link

https://github.com/IlanCosman/tide is the usual recommendation for a powerlevel10k-like experience.

Prompt - https://github.com/IlanCosman/tide. Go fish and never look back.

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