> fish’s command substitution syntax has been extended: $(cmd) now has the same meaning as (cmd) but it can be used inside double quotes<p>That's pretty big news for a more POSIX-like behaviour!
I've been using fish for 2 years now and I pretty much live in the terminal. I would feel handicapped without it.<p>Just use fish and use shebangs `#!/bin/sh` (which should be in your scripts anyways) and you can keep writing/running POSIX scripts all day. I think it's the best option until nushell[0] is ready.<p>As an added bonus now that you don't use bash interactively you can substitute dash[1] and increase the speed of most POSIX scripts, win-win.<p>I'd also recommend zoxide[2], i feel like it's one more must have no matter what you do in the shell.<p>[0]: <a href="https://github.com/nushell/nushell" rel="nofollow">https://github.com/nushell/nushell</a>
[1]: <a href="http://gondor.apana.org.au/~herbert/dash/" rel="nofollow">http://gondor.apana.org.au/~herbert/dash/</a>
[2]: <a href="https://github.com/ajeetdsouza/zoxide" rel="nofollow">https://github.com/ajeetdsouza/zoxide</a>
Fish is so great! I'm a user for 7 years. The autocomplete suggestions are so helpful!<p>However, since using Github Copilot I'm expecting a bit smarter suggestions. I wonder if anyone has tried putting a GPT-3 like engine behind command line autocomplete suggestions. Or maybe the Copilot team offer a sort of API for this.
Any other long-suffering bash user switched to fish and never looked back? Why? Have you switched and ended up coming back to bash? Why?<p>- Long-suffering bash user
Just loving every single bit of it since I switched to it. Had a couple of thoughts of migrating to zsh mostly because its more POSIX compliant but it doesn't look like such a valid argument as time passes by
I used OhMyZsh for years with the Agnoster power line theme and over the years it got slower and slower. Tried Fish about 6 years ago and immediately spent the rest of the day tweaking an Agnoster theme to my liking because everything about it was better than Zsh and waaaay faster. My fork is here [0] for anyone interested, though the readme and screenshots are from the original.<p>[0] <a href="https://github.com/drcongo/agnoster" rel="nofollow">https://github.com/drcongo/agnoster</a>
I feel productive with my Alacritty + Fish (with a starship.rs prompt) setup. I can even swap the shell, and I get the same user experience.<p>It's consistent and blazing fast, and that's all I ask.
I'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).<p>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.
What about Oh My Fish <a href="https://github.com/oh-my-fish/oh-my-fish" rel="nofollow">https://github.com/oh-my-fish/oh-my-fish</a>
Has it been upgated to support new version?
Does anyone know how to disable the bright red color when you first start typing a word? I find it very distracting (specially on over-saturated wide gamut displays) and went back to zsh because of it.
I love fish. It helped me get into linux terminal. It really accelerates the learning curve and turbocharges explorability. I wish more TUI types of apps took hints from fish’s UX
See last weeks discussion:<p><a href="https://news.ycombinator.com/item?id=30660587" rel="nofollow">https://news.ycombinator.com/item?id=30660587</a>
Wanted to love/daily-drive fish but the incompatibility with bash/zsh made things more troublesome than I had the time and patience for.<p>Exciting to see it inching toward POSIX compatibility