Microsoft/vscode

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

Fermée

#209 072 ouverte le 28 mars 2024

 (7 commentaires) (0 réaction) (1 personne assignée)TypeScript (39 847 forks)batch import
buggood first issueteam-low-hangingwindowsworkbench-cli

Métriques du dépôt

Stars
 (184 936 étoiles)
Métriques de merge PR
 (Merge moyen 11h 43m) (1 000 PRs mergées en 30 j)

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.

Guide contributeur