Microsoft/vscode

CLI on Windows: --folder-uri option only works as the last argument and when the --wait option is not present

Closed

#209.072 geöffnet am 28. März 2024

Auf GitHub ansehen
 (7 Kommentare) (0 Reaktionen) (1 zugewiesene Person)TypeScript (74.848 Stars) (10.221 Forks)batch import
buggood first issueteam-low-hangingwindowsworkbench-cli

Beschreibung

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.87.2
  • OS Version: Windows 10 Pro 19044.2486 VM

Steps to Reproduce:

  1. Case where --folder-uri is not the last option. Run code --folder-uri vscode-remote://ssh-remote+vscode@some-workspace --disable-extension ms-vscode-remote.remote-containers --new-window --wait. Command will return immediately without action or error.
  2. Case where --folder-uri is the last option but --wait is present. Run code --disable-extension ms-vscode-remote.remote-containers --new-window --wait --folder-uri vscode-remote://ssh-remote+vscode@some-workspace. Command will return immediately without action or error.

There seems to be a behavior where the the code command silently errors when --folder-uri and the --wait options are used together. Also, there seems to be a bug where the the code command silently errors when the --folder-uri option is not the last option.

Contributor Guide