Open Zamana opened 2 months ago
Hi @Zamana On remote systems, Warp supports bash
, zsh
. Set the default shell to one of the supported and the SSH wrapper should work.
As a workaround you can add command ssh
to your Settings > Subshells > Added commands
menu, then run command ssh <user@server>
to connect to remote session, this will attempt to enable Warp features as a subshell. The subshell method also supports fish
shell.
You can also try disabling the SSH Wrapper by navigating to Settings > Features
. Blocks will stop working but with it disabling, SSH should work as normal.
Related docs: https://docs.warp.dev/features/ssh https://docs.warp.dev/features/subshells
On a related note, we're tracking support for Warp on FreeBSD here. https://github.com/warpdotdev/Warp/issues/3248
If those don't work, please let us know.
@Zamana did changing the default shell on freebsd system to bash or zsh help with the ssh wrapper?
Hello.
I haven't had the opportunity to apply this workaround. The FreeBSD system is hardened by the customer in such a way that I am not allowed to use any shell other than the default one.
And I don't have any other FreeBSD to test on at the moment.
But thanks for the suggestion.
Dupe Check
Describe the bug
When logging in on a FreeBSD system, with CSHELL as default shell, Warp tries to "run" the init files, and shows this: