Remote Development breaks Semantic Coloring

[ablackle]

Using VSC's Remote Development extension pack.
Using RHEL 7 as a server, and Windows 10 as a client.
C/C++ 0.24.0 installed on the server.

Semantic coloring is missing instances. This does not occur in my local Windows VSC, local Windows VSC Insiders, or remote RHEL VSC (via VNC).

This is the expected result.

This is the image with the missing coloring.

[ablackle]

Updated because I can't proof read.

[Colengms]

Hi @ablackle . Thanks for reporting this. This is currently a limitation, as there is not an API to access color settings in themes ( microsoft/vscode#32813 ). We parse the current theme file directly to look up colors. When remoting, cpptools is running on the remote machine, but the themes are on the local machine, so cpptools is unable to access them. Colors overridden in user settings are applied, however. We are working with the core VS Code team on better facilitating semantic colorization, and will revisit this as soon as we can.

[joelspadin]

Do you have any examples for how to override colors in user settings? It would be nice if I could just copy colors from my theme into settings until this gets properly fixed.

I tried setting several of the scopes listed on https://code.visualstudio.com/docs/cpp/colorization-cpp in my remote machine's settings.json, but nothing changed. What I tried:

    "editor.tokenColorCustomizations": {
        "textMateRules": [
            {
                "scope": [
                    "variable.other.local",
                    "variable.other.global",
                    "variable.parameter",
                    "variable.other.property.cli"
                ],
                "settings": {
                    "foreground": "#FF0000"
                }
            }
        ]
    }

[Colengms]

Hi @ChaosinaCan . Thanks for reporting this. It looks like the failure to find the theme files may be causing semantic colorization to abort instead of proceed with what settings are available. I will investigate.

Also, there are a number of scopes not included in the documentation (as they were existing scopes, not newly added), which would also need to be added in settings, as we are also reading those from theme files. We'll need to publish a full list to enable working around the issue using settings.

If you haven't already, please upvote this issue: microsoft/vscode#32813 :)

[joelspadin]

Already upvoted. Thanks!

[drldavis]

I'm having the same problem when using Windows Subsystem for Linux. Anyone find any solutions?

[jheaff1]

I too would very much like to have this issue resolved. Until the enhanced colorization is functional via remote development, I will continue to use the clunky Eclipse C++ editor