3 ms·

I don't remember the root cause as it was a while ago now, but in my case I couldn't login on a TTY because of that.

• pxc 5y ago
  That would be a nightmare for sure. I can't blame you for being cautioned by an experience like that. I've been running Fish as my login shell for almost 10 years now, on Linux and then additionally for ~4 years for intermittent macOS usage (only at work) without issue. I don't really like launching Fish from ~/.bash_profile because or similar because I don't like having to type `exit` twice to exit, and `exec`ing into Fish leaves you in one shell but with your $SHELL variable set to another. But if that works for you, more power to ya, and it's good for Fish users to know that that's an option if they run into issues using Fish as a login shell.
  • boudin 5y ago
    Now that you say that, that's funny as I do not have to exit twice. I don't know why though as it seems that it should be the case.
    • pxc 5y ago
      Does your profile call `exec fish -i` rather than just `fish -i`? In that case, you'll only exit once :) From the `exec` manual: If exec is specified with command, it shall replace the shell with command without creating a new process. If arguments are specified, they shall be arguments to command. Redirection affects the current shell execution environment. https://man7.org/linux/man-pages/man1/exec.1p.html https://man7.org/linux/man-pages/man1/exec.1p.html
      • boudin 5y ago
        I do `exec fish` indeed, so that's the reason.