VSCode Remote-SSH setup hangs when using fish shell

I previously mentioned that VSCode’s Remote-SSH feature wasn’t working with my jump-host-proxied server. Well, I think I figured out why. It wasn’t the jump host that was the problem. Rather, VSCode’s SSH plumbing doesn’t play well with my beloved fish shell. See this thread, for example. I’ve spent a fairly comical amount of time coming up with alternative workflows, including some big ones I haven’t had the chance to write about yet, when all I needed to do to fix this was add the following to my ~/.profile and ~/.bashrc: case $- in *i*) exec fish ;; esac That’ll switch to fish in an interactive shell and otherwise stick with bash, letting VSCode do its thing. Luckily I had fun and learned stuff while building out the alternatives. Otherwise I’d be slightly horrifed atm.