`VSCODE_EXTENSIONS` not working on macOS about vscode HOT 4 CLOSED

See #169600 for a similar (same?) issue but this point was not resolved.

from vscode.

The ~/.vscode folder will still be created even if the environment variable points elsewhere

This is not only used for extensions but also for other features like argv.json and cli. Please check if your extensions are being read from the folder you set in the env variable?

from vscode.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

from vscode.

I have just symlinked the folder so not a massive issue, but it did appear to recreate the extensions folder in ~/.vscode evertytime even though VSCODE_EXTENSIONS was set elsewhere so I assume it was not reading from the set location.

from vscode.