Microsoft/vscode

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

已关闭

#209,072 创建于 2024年3月28日

 (7 条评论) (0 个反应) (1 位负责人)TypeScript (39,847 个派生)batch import
buggood first issueteam-low-hangingwindowsworkbench-cli

仓库指标

星标
 (184,936 个星标)
PR 合并指标
 (平均合并 11小时 43分钟) (30 天内合并 1,000 个 PR)

描述

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.

贡献者指南