-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Enable the SemanticTokensFeature by default #3899
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
Conversation
This is covered under vscode's "editor.semanticHighlighting.enabled" setting plus the user has to have a theme that has opted into highlighting. Bumps required vscode stable to 1.44
bors r+ 🎉 |
Build succeeded |
Note that we could remove |
Yup, my thoughts exactly! We also have one bit of proposed api about call
hierarchy (?).were there any updates on that?
…On Wednesday, 8 April 2020, Jeremy Kolb ***@***.***> wrote:
Note that we could remove "enableProposedApi": true at this point but I
think we should leave it since we'll need it later on.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3899 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANB3MZRWYUA6PTHEZVCZFLRLTQFTANCNFSM4MEF65FA>
.
|
No the vscode api is stable but LSP is still proposed I think. The
distinction is... a little confusing which is why I updated the comment.
On Wed, Apr 8, 2020, 6:27 PM Aleksey Kladov <[email protected]>
wrote:
… Yup, my thoughts exactly! We also have one bit of proposed api about call
hierarchy (?).were there any updates on that?
On Wednesday, 8 April 2020, Jeremy Kolb ***@***.***> wrote:
> Note that we could remove "enableProposedApi": true at this point but I
> think we should leave it since we'll need it later on.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <
#3899 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AANB3MZRWYUA6PTHEZVCZFLRLTQFTANCNFSM4MEF65FA
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3899 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBACRHPEIKYQXO7KG2O6QLRLT24BANCNFSM4MEF65FA>
.
|
I'm going to reverify this after updating |
Woah, you mean we can use semantic highlighting in stable now? Nice!! |
Yes with latest vscode stable and a theme (the default ones work) that supports it. |
Can I have a link on what a theme needs to havo in order to support this feature? (I have my own theme) Thank you :D |
I wonder if they have like, ... the actual docs for this? |
Is semantic highlighting only available on vscode? Or does emacs support it too? |
Vscode for sure. I don't know about emacs.
…On Fri, Apr 17, 2020, 10:29 AM Luis Wirth ***@***.***> wrote:
Is semantic highlighting only available on vscode? Or does emacs support
it too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3899 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBACRARDILUNLAOVIS5UILRNBRWJANCNFSM4MEF65FA>
.
|
support is not yet implemented in emacs: emacs-lsp/lsp-mode#1482 |
Android: Added support for prctl handling thread names Addresses the first part of rust-lang#3618.
This is covered under vscode's "editor.semanticHighlighting.enabled"
setting plus the user has to have a theme that has opted into highlighting.
Bumps required vscode stable to 1.44
Closes #3773