Command line don't work as specified in the docs

[justanotheranonymoususer]

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

Version: 1.75.1 (user setup)
Commit: 441438a
Date: 2023-02-08T21:32:34.589Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

Steps to Reproduce:

1. Look at the command-line docs, which say to run as: code.exe [options][paths...]
2. Run code.exe --disable-gpu-sandbox C:\test
3. Observe that the folder doesn't open
4. Close editor
5. Run code.exe C:\test --disable-gpu-sandbox
6. Observe that the folder opens

[joaomoreno]

Where is --disable-gpu-sandbox documented, exactly?

[justanotheranonymoususer]

Here:
https://code.visualstudio.com/docs/setup/windows#_unable-to-run-as-admin-when-applocker-is-enabled

With the introduction of process sandboxing (discussed in this blog post) running as administrator is currently unsupported when AppLocker is configured due to a limitation of the runtime sandbox. If your work requires that you run VS Code from an elevated terminal, you can launch code with --no-sandbox --disable-gpu-sandbox as a workaround.

[joaomoreno]

From microsoft/vscode-docs@5153a91, cc @bpasero. I can't find ourselves handling --disable-gpu-sandbox anywhere... I bet minimist thinks it's a string option and is allowing it to eat up the folder path.

[bpasero]

cc @deepak1556