-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Highlight 2nd namespace when nested #3023
Comments
Our extension doesn't implement colorization. It looks like it will be fixed once VS Code switches to the atom/language-c tree sitter implementation: microsoft/vscode#50140 . |
Oh, cool, thanks for the info.
…On Fri, Jan 11, 2019, 00:18 Sean McManus ***@***.***> wrote:
Our extension doesn't implement colorization. It looks like it will be
fixed once VS Code switches to the atom/language-c tree sitter
implementation: microsoft/vscode#50140
<microsoft/vscode#50140> .
[image: image]
<https://user-images.githubusercontent.com/19859882/51011206-819f4380-150c-11e9-9a92-6cb0ae98a977.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3023 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFbgK8Qgo9c1ILtZQAy16vG2rAY6DdL6ks5vCAKVgaJpZM4Z6iMx>
.
|
This has been fixed with the latest VS Code -- all the namespaces are non-highlighted. |
Actually, the fix is in VS Code Insiders (not VS Code, unless you install the Better C++ Syntax extension). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Type: LanguageService
Super minor, and annoying, feature request.
Screenshots
Additional context
My c_cpp_properties.json:
The text was updated successfully, but these errors were encountered: