Remove .vscode from version control

[diraven]

Description

.vscode settings being in VCS forces everybody to use them and prevents customization. Workspace settings override user settings. Which means you effectively can't customize workspace settings for this project at all without your changes ending up in VCS, which is very likely an undesirable outcome.

I believe the right thing to do here would be:

• Renaming .vscode to something like sample.vscode in VCS and ignoring .vscode itself.
• Possibly also adding automatic copying of sample.vscode to .vscode if .vscode does not exist into RUN_THIS.py.

That way we can still distribute configuration changes/templates if need be with devs retaining the ability to change their local workspace settings including settings.json, tasks.json and launch.json.

[diraven]

I'll make a PR for it later if there are no hard objections to this.

[PJB3005]

Doesn't VSCode have a "default workspace settings" system exactly for this purpose?

[osjarw]

Not an expert on these particular settings, but stuff like formatter settings definitely should belong in the workspace settings.

[diraven]

Doesn't VSCode have a "default workspace settings" system exactly for this purpose?

Didn't find such functionality in VSCode. Only thing I found is this ancient issue, which was not worked on yet it seems. You got a link?

Not an expert on these particular settings, but stuff like formatter settings definitely should belong in the workspace settings.

It probably should. But that's a bit out of scope for this issue.