-
https://reddit.com/r/neovim/comments/12gvms4/this_is_why_your_higlights_look_different_in_90/
-
# Bug Report
Function identifiers (including methods) don't appear to be receiving semantic highlighting tokens from the LSP as of TS 4.2.x.
This is important to me because I prefer the terser sty…
-
Feature request to support textDocument_semanticTokens, now part of official LSP standard:
https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_se…
-
(This is as much a feature request both for the server itself and the VSCode extension.)
I'm currently using texlab with a customised syntax highlighting extension for VSCode (https://marketplace.v…
-
The syntax/semantic analysis APIs should now be sufficient for a basic LSP implementation. We don't need to be super ambitious here - just performing [semantic highlighting](https://microsoft.github.i…
-
After enabling it in the package's settings, is there anything else that needs to be done? Do I need to switch the syntax in Atom to "Plain Text" or something?
-
Add support for semantic highlighting.
-
Normally, highlighting is ok, but when an LSP kicks in, it recolors some of the identifiers wrongly (mainly variables)
Before LSP:
![just-tree-sitter](https://user-images.githubusercontent.com/513…
-
Highlight source code according to semantic properties, example:
-function declaration names
-type declaration names
-variable names
-
Nimsuggest supports semantic highlighting through which it has been implemented in the nvim plugin https://github.com/alaviss/nim.nvim. Request to implement it for vscode :D
ghost updated
3 years ago