Make extension respect the window.openFoldersInNewWindow setting

[jonpetersathan]

It would be convenient, if the remote extension would also respect the window.openFoldersInNewWindow setting of vscode. This way you could use eg. code ./myproject instead of code -r ./myproject in a remote workspace to replace the current window.

[aeschli]

Can you give details? Which remote extension? What are the steps to reproduce?

[jonpetersathan]

This affects all remote extensions (SSH, Containers, WSL).

Steps to Reproduce

• Change window.openFoldersInNewWindow to off in vscode settings
• Open a remote workspace (eg. wsl ubuntu)
• Run code ./myproject/ from the integrated terminal of the remote workspace

Current Behavior

• VSCode opens up in a new window

Expected Behavior

• VSCode should replace the current opened window with ./myproject/ (What happens if you run code --reuse-window ./myproject

The window.openFoldersInNewWindow option basically changes the default behavior of vscode on startup. If turned on (default) and another instance is started, vscode will open up in a new window. If this setting is turned off, vscode will replace the current opened window with the specified folder (in the example above ./myproject/.
This behavior can also be forced with the command line arguments --reuse-window or --new-window respectively.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• window.openFoldersInNewWindow seems hiding new windows (#40796)