To properly fix microsoft/vscode#123332 node-pty must provide a way to control argv[0] of the spawned process, that is, instead of…
const ptyProcess = (await import('node-pty')).spawn("/bin/sh", ["--login"], options);
… which internally does an…
execv("/bin/sh", "/bin/sh", "--login", NULL);
… vscode must do something like…
const ptyProcess = (await import('node-pty')).spawna("/bin/sh", "-sh", [], options);
// or
const ptyProcess = (await import('node-pty')).spawna("/bin/sh", ["-sh"], options);
… which internally does an…
execv("/bin/sh", "-sh", NULL);
… so a new API will be needed, unless this can be put into options somehow, perhaps…
const ptyProcess = (await import('node-pty')).spawna("/bin/sh", [], {"argv0": "-sh"});
To properly fix microsoft/vscode#123332 node-pty must provide a way to control
argv[0]of the spawned process, that is, instead of…… which internally does an…
… vscode must do something like…
… which internally does an…
… so a new API will be needed, unless this can be put into
optionssomehow, perhaps…