I absolutely love fish. Completions and colors and all that are nice but the killer feature for me is the scripting. I can actually throw a loop or a one-off function together for whatever random task I have and not have to worry about arcane syntax or weird gotchas.
I used bash for years and anything that requires more than some pipes would either not get done or get done in a heavier-duty programming language. With fish things just made sense and I was immediately solving more complex problems at the shell.
Fish Shell 3.2
131–133 of 133 posts
Re: Fish Shell 3.2
#132I think Fish is an excellent interactive shell. I've still got Bash as my default shell for non-interactive sessions, but I configured Konsole to start Fish by default for interactive use (Settings->Command, set to the path to the fish executable). That way scripts that need Bash still work, but I get a sane environment for interaction. For "portable" scripts I write POSIX shell, C, or Python, depending on what I nee…
Shebangs direct scripts to the right interpreter. Setting a default interactive shell won’t override it.
True, but there do exist (crappy) scrips with incorrect shebangs. EG specifying `#!/bin/sh` when they should use `#!/usr/bin/env bash`, since `/bin/sh` isn't necessarily bash. Could be dash. Could be fish. Could be oil. Etc.)
Re: Fish Shell 3.2
#133Earlier quoted context omitted.
Shebangs direct scripts to the right interpreter. Setting a default interactive shell won’t override it.
True, but there do exist (crappy) scrips with incorrect shebangs. EG specifying `#!/bin/sh` when they should use `#!/usr/bin/env bash`, since `/bin/sh` isn't necessarily bash. Could be dash. Could be fish. Could be oil. Etc.)
I think /bin/sh is required to be a POSIX shell, at least when invoked with that name, and fish wouldn’t qualify.