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 opened on Mar 28, 2024

 (7 comments) (0 reactions) (1 assignee)TypeScript (39,847 forks)batch import
buggood first issueteam-low-hangingwindowsworkbench-cli

Repository metrics

Stars
 (184,936 stars)
PR merge metrics
 (Avg merge 11h 43m) (1,000 merged PRs in 30d)

Description

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