People who have replaced fish with something else (other than bash and zsh) after using it for a significant time, to what and why?
I used fish for a few years and finally switched to zsh. I wouldn't consider myself a super shell power user, so eventually I got tired of trying to make standard things work (such as nvm and similar helper utilities). Yes there are workarounds and solutions but I just wanted plug and play for stuff I'd find in the wild. Turns out that zsh with ohmyzsh has much of fish's functionality (that I utilized anyway), so I'm…
Fish 3.4.0
61–70 of 93 posts
Re: Fish 3.4.0
#62Any other long-suffering bash user switched to fish and never looked back? Why? Have you switched and ended up coming back to bash? Why? - Long-suffering bash user
Re: Fish 3.4.0
#63Any other long-suffering bash user switched to fish and never looked back? Why? Have you switched and ended up coming back to bash? Why? - Long-suffering bash user
In December just gone I gave up on macOS after 17 years and switched to Linux. Thought I’d take the opportunity to try a new shell and went for fish (though I still use bash on certain remote hosts for a variety of reasons).
autocomplete and colours/highlighting are more than enough to keep me using it. I really enjoy them. But…
I don’t yet love how history works. Four months in, I still can’t get used to not having ctrl-r.
I miss the symmetry of `do … done` in loop syntax, finding `for … end` jarring.
The lack of !! really grates sometimes. I was going to say I miss `^x^y` last command modification, but actually I can’t recall trying it since switching.
`VAR=x cmd …` doesn’t seem to work quite how I expect. I have an alias/function to perform SSO login to AWS, which expands to `BROWSER=otherfunc aws sso login` - otherfunc itself expanding to `firefox -P workprofile`. This stubbornly opens a Firefox tab in some random window, regardless of profile - despite otherfunc on its own always working. I did not, IIRC, have this trouble with bash.
Re: Fish 3.4.0
#64Any other long-suffering bash user switched to fish and never looked back? Why? Have you switched and ended up coming back to bash? Why? - Long-suffering bash user
Switched and came back after about 3 years (to zsh). Fish is nice in many ways, but it kinda lives up to its "A command line for the 90's" slogan. It's better than what came before it, but I'm not sure it's better enough . Using a non-POSIX shell can feel like death by 1000 cuts sometimes, and I wasn't sure the benefits of Fish were worth the cost. Also, scripting feels like a bit of an afterthought in Fish and that'…
Re: Fish 3.4.0
#65Unfortunately, mc has been broken since 3.2.0 IIRC and nobody's working on it.
Re: Fish 3.4.0
#66I've just taken Fish for a test drive and I'm really impressed. I use the Starship prompt in Zsh and it worked out of the box in Fish. It appears direnv will too (which I rely on). The one thing I can't work out is how to change the cursor to a block, it's a line. No vi-mode or anything, just a nice rectangle. I tried `set fish_cursor_default block` to no avail.
Re: Fish 3.4.0
#67Any other long-suffering bash user switched to fish and never looked back? Why? Have you switched and ended up coming back to bash? Why? - Long-suffering bash user
Re: Fish 3.4.0
#68Any other long-suffering bash user switched to fish and never looked back? Why? Have you switched and ended up coming back to bash? Why? - Long-suffering bash user
Then I tried switching to zsh with oh-my-zsh and all that. 42 million tunable bits and I still didn't get it to my liking.
Then I found Fish and 95% of the stuff was good enough out of the box. The only things I've really added was Starship[0] as a prompt - again good enough with pretty much zero configuration and fzf[1] for history search.
Now I use it everywhere, synced via Homeshick[2]
I still use bash to write shell scripts that aren't long enough to be converted to Python though.
[0] https://starship.rs [1] https://github.com/jethrokuan/fzf [2] https://github.com/andsens/homeshick
Re: Fish 3.4.0
#69> fish’s command substitution syntax has been extended: $(cmd) now has the same meaning as (cmd) but it can be used inside double quotes That's pretty big news for a more POSIX-like behaviour!
They did it also because with the old syntax it was unintuitive how to put commands inside quotes. It borrowed the new syntax from bash but it wasn't ONLY to be more bash compatible. It solved a real fish shell problem also.
Re: Fish 3.4.0
#70> fish’s command substitution syntax has been extended: $(cmd) now has the same meaning as (cmd) but it can be used inside double quotes That's pretty big news for a more POSIX-like behaviour!