3 ms·

I started using fish several years ago on the recommendation of a friend and never looked back. It's the must-install shell of every machine I own. Fish occasi

I started using fish several years ago on the recommendation of a friend and never looked back. It's the must-install shell of every machine I own. Fish occasionally has the rare syntax quirk I need to drop into bash for, but the autocomplete is so next level I simply can't use a plain shell anymore.

pkulak 5y ago
Looks like the major syntax quirk just went away: > fish’s command substitution syntax has been extended: $(cmd) now has the same meaning as (cmd) I never really understood the appeal of maintaining perfect bash compatibility in your prompt. The only time I've ever needed that was because I'm copy/pasting something from the internet, which I probably shouldn't be doing at all, and at the very least not with such frequency that it effects my decision of which shell to use.
- setuids 5y ago
  > The only time I've ever needed that was because I'm copy/pasting something from the internet, which I probably shouldn't be doing at all, and at the very least not with such frequency that it effects my decision of which shell to use. It is nice when you generally write {POSIX,Bash} scripts, and decide to quickly throw something together in the interactive shell. I find myself often putting $(), before realising that I need to remove the $ to make it valid in fish. But yeah, i think it's mostly to make shell scripts of the internet work OOTB.
AnonC 5y ago
I’m interested to learn more about why you never looked back (or probably didn’t use anything else) once you tried Fish shell; like what it offered that was so compelling and what you saw lacking in other shells (I’m fine with the fact that this may probably be specific to your needs).
- em-bee 5y ago
  probably the biggest thing for me is that command substitution translates output into arguments by line so that things like rm (cat list-of-files) just work without any quoting nightmare regardless of what kind of weird characters are in filenames (well, at least as long as they don't contain newlines). that just simplifies working on the commandline a lot. search feels more convenient although the difference seems superficial and i can still see room for improvement (i'd like to be able to type two words and then search for commands with those two words in any position) the syntax and other things like array handling feel a lot cleaner. multi line commandline editing felt like a great idea too although the use was not very intuitive (i think they removed that feature?)
- confident_inept 5y ago
  The auto-complete is just that good. It will autocomplete options for arbitrary programs intelligently. For example I use sshfs on a few different machines in my home and can simply type the name of the program and press the up arrow to get the list of every previous sshfs command string I've entered. It uses a history file like bash but can pick out only the things pertaining to the program I'm trying to run.
doubled112 5y ago
I really like the fish syntax and feature set on paper. My biggest problem with fish is that my muscle memory is still Bash/POSIX, and training it out of me wasn't working. ZSH autocomplete plus autosuggestions plus syntax highlighting got me close enough, and the muscle memory is backwards compatible when I touch somebody else's machine or server.

pkulak 5y ago

Looks like the major syntax quirk just went away: > fish’s command substitution syntax has been extended: $(cmd) now has the same meaning as (cmd) I never really understood the appeal of maintaining perfect bash compatibility in your prompt. The only time I've ever needed that was because I'm copy/pasting something from the internet, which I probably shouldn't be doing at all, and at the very least not with such frequency that it effects my decision of which shell to use.

setuids 5y ago
> The only time I've ever needed that was because I'm copy/pasting something from the internet, which I probably shouldn't be doing at all, and at the very least not with such frequency that it effects my decision of which shell to use. It is nice when you generally write {POSIX,Bash} scripts, and decide to quickly throw something together in the interactive shell. I find myself often putting $(), before realising that I need to remove the $ to make it valid in fish. But yeah, i think it's mostly to make shell scripts of the internet work OOTB.

AnonC 5y ago

I’m interested to learn more about why you never looked back (or probably didn’t use anything else) once you tried Fish shell; like what it offered that was so compelling and what you saw lacking in other shells (I’m fine with the fact that this may probably be specific to your needs).

em-bee 5y ago
probably the biggest thing for me is that command substitution translates output into arguments by line so that things like rm (cat list-of-files) just work without any quoting nightmare regardless of what kind of weird characters are in filenames (well, at least as long as they don't contain newlines). that just simplifies working on the commandline a lot. search feels more convenient although the difference seems superficial and i can still see room for improvement (i'd like to be able to type two words and then search for commands with those two words in any position) the syntax and other things like array handling feel a lot cleaner. multi line commandline editing felt like a great idea too although the use was not very intuitive (i think they removed that feature?)
confident_inept 5y ago
The auto-complete is just that good. It will autocomplete options for arbitrary programs intelligently. For example I use sshfs on a few different machines in my home and can simply type the name of the program and press the up arrow to get the list of every previous sshfs command string I've entered. It uses a history file like bash but can pick out only the things pertaining to the program I'm trying to run.

doubled112 5y ago

I really like the fish syntax and feature set on paper. My biggest problem with fish is that my muscle memory is still Bash/POSIX, and training it out of me wasn't working. ZSH autocomplete plus autosuggestions plus syntax highlighting got me close enough, and the muscle memory is backwards compatible when I touch somebody else's machine or server.