Closed Sergeytata closed 3 years ago
Specifying -l
would be a must so that remote bash is loaded as a login shell and specifying the specific path to the shell to be used. This allows for bashrc to be properly loaded with bash completions and all.
The remote ssh extension can be configured using the following remote file ~/.vscode-server/data/Machine/settings.json
:
{
"terminal.integrated.shell.linux": "/bin/bash",
"terminal.integrated.shellArgs.linux": [ "-l" ],
}
Currently, my systemd
, git
, etc bash auto-completions are unavailable when opening the ssh shell through the SSH FS action.
These are available when manually launching ssh myuser@myhostname
without any option and when opening a terminal using the remote ssh extension when configured as above.
Config option added in 65fa99b and added in the UI in 40e2d12:
By default it uses
$SHELL
as "command", which should be "The user's shell, as specified by the password database.", but which you can override. You're free to use e.g. $SHELL -l
for your configs.
I've looked for this in the past, but I never found a proper answer:
-l
option? Is it like a documented or even unspoken/undocumented rule?-l
to $SHELL
(whatever that resolves to) lead to any issues?Since I couldn't find answer to 1. and with 2. in mind, I decided to not pass -l
by default.
I would like to open a remote SSH terminal with the options allowing X forwarding. I normally use
ssh -XYC username@ip
. Is it possible to modify the command somewhere?