VS Code ignores any unknown command line options instead of showing an error

[segevfiner]

• VSCode Version: 1.27.2
• OS Version: Windows 10.0.17134.285 x64

Steps to Reproduce:

1. Run code --foo bar
2. VS Code launches successfully.

I'd expect giving unknown options to error out so as to catch typos, unsupported options, and what not. To do this we probably need to use the unknown option for the minimist parser at src/vs/platform/environment/node/argv.ts. I guess it should print an error and process.exit(2).

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

[ntpttr]

I'd like to give this a shot and assign the issue to myself.

[ntpttr]

Pull request is available for this here: #59806

[bpasero]

@aeschli didn't you do this?

[segevfiner]

@bpasero I think it was decided not to do this because this is how vs code handles supporting Chromium's assortment of CLI flags. (Guess it doesn't have the function to strip them out after it parses them or something similar...)

Look at the PR.

[aeschli]

Yes, since September we now warn if an unknown command line argument is used.
Duplicate of #78831