They warn about it on their home page, so I assumed using it could bust your system. My bad.
I think they also had harsher wording about this in the past but I might be misremembering…
This was more of a problem when they didn’t support basic POSIX-isms so even basic calls to sh like sh -c 'echo"foo" && echo "bar"' would fail. Less of a problem now but you never know when a random script is going to rely on some obscure POSIX flag
I thought you weren’t supposed to use Fish as your login shell directly since it isn’t fully POSIX compatible
Why would your login shell need to be fully POSIX compatible?
They warn about it on their home page, so I assumed using it could bust your system. My bad.
I think they also had harsher wording about this in the past but I might be misremembering…
This was more of a problem when they didn’t support basic POSIX-isms so even basic calls to
shlikesh -c 'echo "foo" && echo "bar"'would fail. Less of a problem now but you never know when a random script is going to rely on some obscure POSIX flagScripts who use
#!/bin/share independent of your login shell.What does any of that have to do with your login shell?