colourization not working #5769
Labels
Feature: Colorization
Language Service
more info needed
The issue report is not actionable in its current state
Comments
|
I should also note that when I mouse over the macros, they appear in the popup. If I right click on them and Go To Definition, the source file opens. So, it appears Intellisense is working. I am using compileCommands.json. Here is the log diagnostics for the file selected in the above screenshots: |
|
Hi @sslupsky . I believe you are seeing an issue with IntelliSense not working, not semantic colorization specifically. Note in your diagnostics output it indicates, "not ready", which implies that we haven't received a response from the IntelliSense process yet. Hover and Go To Def can work without IntelliSense results. Could you provide log output, using |
Colengms
added
Language Service
more info needed
|
@Colengms Apologies, I was away last week. I added the settings to my settings.json and restarted vscode. The log output doesn't appear to have changed: Though, the "not ready" does not appear in this output. I noticed the vscode updated to 1.47.2 today as well. Note however, the colourization issue still remains and the colours are not working properly. Here is the output from the main log window: I am not sure what this error message refers to. In the middle of all that, there is a message indicating that the Intellisense server was terminated: But further on, the appears to be running again. I thought this might have something to do with the "intelliSenseMode" settings. It was previously set to gcc-x86. I noticed there are several "new" settings here now. So, I changed it to gcc-arm and gcc-arm64 to see if that made a difference. The output above is with the option set to "gcc-arm" and is essentially the same as when the settings is set to "gcc-x86". |
|
I disabled the "Arduino" extension. That cleaned up the error message in the log (Main) output: However, the C/C++ output window still shows the "Failed to query compiler" messages and the Intellisense server shutdown message. |
|
FYI, my vscode is set up for development with the Zephyr RTOS. The target is an ARM Cortex M0 32-bit micro controller. I use the arm-none-eabi-gcc toolchain. More specifically, I have the "8-2018-q4-major" version of this toolchain installed. /usr/local/bin/arm-none-eabi-gcc is a link as follows: |
|
I downgraded the Intellisense extension to version 0.28.3 and the colourization works as before. So, this issue appears to be related to 0.29.0-insiders2 The C/C++ log output for 0.28.3 appears to be similar to what I observed for 0.29.0-insiders2: |
|
Hi @sslupsky. Each time you see "cpptools/finishUpdateSquiggles" indicates a successfully completed intelliSense pass. I see the following in your log output: "cpptools/getSemanticTokens". This indicates the semantic tokens request is being processed. Could you try invoking the "Developer: Inspect Editor Tokens and Scopes", and clicking on something you expect to be colored? This should now indicate semantic token scopes as well as TextMate scopes. If those are indicating that functions and variables, etc., are being identified semantically, it would seem to be a theme issue. What Color Theme are you using? It's technically possible for a theme to opt out of semantic highlighting. I also see the following in your log output: "Error squiggle count: 2". Is it possible that what these squiggles point to may be preventing the file from being parsed properly? 0.29.0 completely removes our original implementation of semantic colorization, which had been applying decorations directly to the editor, and instead uses VS Code's new Semantic Tokens API. Since you are seeing "cpptools/getSemanticTokens" messages processed, that 'provider' appears to be enabled properly. Are you able to get semantic colorization with any other source files or projects? You could use "Developer: Inspect Editor Tokens and Scopes" to confirm that with 0.29.0. |
|
This issue has been closed automatically because it needs more information and has not had recent activity. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Type: LanguageService
Since release of 0.29.0-insiders2, colourization stopped working
Describe the bug
Version: 1.47.0
Commit: d5e9aa0227e057a60c82568bf31c04730dc15dcd
Date: 2020-07-09T08:01:54.115Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 18.7.0
colourization of macros, types and dimming has stopped working.
I have restarted vscode several times. I noticed the problem today, after a scheduled reboot of my computer and the recent vscode updates were applied. Could be related to #5401?
Screenshots
This screenshot shows several enum's that are not coloured properly. The MODEM_PIN macro does not colour properly.
In this screenshot, the last three MODEM_PIN macros should be dimmed.
The text was updated successfully, but these errors were encountered: