vscode not adhering to my syntax highlighting in settings.json unless I open the file and edit one of the colors

[cjolivier01]

• VSCode Version:
• OS Version:

Steps to Reproduce:

1. Open any rermote project
2. Syntax coloring is the default, all other settings appear to be ok
3. edit "editor.background": "#000000", by removing a zero, then saving (screen turns red) then re-adding the zero and saving
4. syntax highlighting is enabled

Does this issue occur when all extensions are disabled?: Yes/No
Not locally, but with only remote ssh plugin enabled, it occurs when I connect to the remote host with all other plugins disabled. It does this on multiple AWS server/project roots.

[aeschli]

What theme do you have configured? Is it set in the user settings or the (remote) workspace settings?

(maybe a duplicate of #101433)

[cjolivier01]

Default Dark+ how do I tell where it's set? It isn't in my settings.json, but when I tab through preferences "Workbench: Color Theme", it shows up on
It does not say "Modified in..." on any of the tabs.
"Color customization" says "modified in workspace"

[cjolivier01]

I tried changing the workspace config to "Visual Studio Dark" so that it weas different from "User", but that didn't help.

[aeschli]

You use the default theme (otherwise it would have a blue bar next to the settings).

`edit "editor.background": "#000000", by removing a zero, then saving (screen turns red) then re-adding the zero and saving

Where did you do this? User settings or workspace settings?

To open the user settings JSON, run Preferences: Open User Settings (JSON)
To open the workspace settings JSON, run Preferences: Open Workspace Settings (JSON)

[cjolivier01]

only settings i ever usually edit are in workspace .vscode/settings.json
I keep the .vscode stuff in a github repo so i can duplicate it everywhere. i don’t even know where the other settings files are :)

[aeschli]

Ok, that's the workspace settings.

The bug that you are seeing is #101433. It's fixed in the latest insiders.

[cjolivier01]

I installed 1.47.0-insider and the problem did not go away. I even uninstalled and reinstalled everything clean.

[aeschli]

Ok, sorry for that, the commit got delayed, bit is in now. Please try with Monday's update.

5069ddc