21–30 of 93 posts
> 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!
> 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!
Finally. I should give it a try now.
Earlier quoted context omitted.
> Always recommend people to use fish if they're not the "customize everything everywhere to my liking" type. Fully agree. It feels like fish is the Apple of shells, in that regard. Unless you really love to tinker with your shell, the great defaults and great UX make it really easy to recommend.
Is Fish difficult to customize? Just curious since I do tend to customize everything to some degree to fit my personal prefs.
That said, I believe that zsh has a bigger community, and therefore most likely a richer ecosystem with more plugins. For example, oh-my-zsh has 142k stars, and oh-my-fish has 8k stars.
However, even with the rich ecosystem of plugins, I wasn't able to get my zsh to be as pleasant to use as my fish, where I only have some self-made customizations (not even using oh-my-fish).
But if having lots of plugins to choose from is important to you, zsh may be a better choice.
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.
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
My company has default shell as zsh so every tool assumes that. How can I switch to fish in such an environment?
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 think POSIX compliance of interactive shells is completely irrelevant. POSIX shells are relevant when you're writing scripts that will be distributed, but there's no reason that needs to be done with the same shell you use interactively. I use fish presently and zsh before that for nearly 15 years, but my shell scripts have always started with #!/bin/sh It's not like fish installs to /bin/sh, nor are /bin/sh script…
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
My company has default shell as zsh so every tool assumes that. How can I switch to fish in such an environment?
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? - Long-suffering bash user
Fish excels as an everyday interactive shell. I never program shell scripts. I write Julia code whenever something equivalent of a shell script is needed. Before that I often used Go.
Fish is so great! I'm a user for 7 years. The autocomplete suggestions are so helpful! 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.
I remember that I was able to replicate this last year, not 100% sure why I'm not using it daily tho. :D
One thing to note, the limited waitinglist he talks about in the video is done, and now you can sign up and "pay" for ~NLP~...ahem CLP tokens as OpenAI calls them