Basically every non-Windows system comes with a POSIX-compliant shell at /bin/sh. If you’re using shebangs in your POSIX shell scripts like you should, using Fish as your Friendly InteractiveShell shouldn’t be a problem.
Don’t try to out-nerd me, your shebang advice isn’t even POSIX compliant ! Use #!/usr/bin/env sh, there are systems (incl. NixOS) where there is no /bin/sh
And Fish’s scripting language leaks into the interactive shell. Setting variables via export a=b doesn’t work, for example. I don’t like that.
even if it was… you can just run bash or /bin/sh and then run the script there. It’s not you can’t shell into a different shell to run a script. you lose nothing.
Basically every non-Windows system comes with a POSIX-compliant shell at
/bin/sh. If you’re using shebangs in your POSIX shell scripts like you should, using Fish as your Friendly Interactive Shell shouldn’t be a problem.deleted by creator
Don’t try to out-nerd me, your shebang advice isn’t even POSIX compliant ! Use
#!/usr/bin/env sh, there are systems (incl. NixOS) where there is no/bin/shAnd Fish’s scripting language leaks into the interactive shell. Setting variables via
export a=bdoesn’t work, for example. I don’t like that.even if it was… you can just run
bashor/bin/shand then run the script there. It’s not you can’t shell into a different shell to run a script. you lose nothing.