ST API: Missing support for textDocument/semanticHighlighting

[junknet]

I only see these scopes:{
markup.error
markup.warning
markup.info
markup.info.suggestion
}
It just for Diagnostics.
How do I get the LSP to analyze my code and return the type name.
for c++ code; such as function , module,struct,keyword.....
Then I can use these to customize my code color !

[rwols]

Both clangd and ccls already publish semantic highlighting. However this notification has not been standardized yet. That said, it's basically impossible to accomplish "dynamic" highlighting with the ST API. I'm not saying it will never happen, but you're swimming upstream if you would try to implement it at this time.

[rwols]

Looks like it's standardized for 3.16 of the protocol. https://github.com/microsoft/vscode-languageserver-node/blob/release/protocol/3.16.0-next.1/protocol/src/protocol.semanticTokens.proposed.ts

Perhaps we can experiment around with view.add_regions.

[pushqrdx]

@rwols so it isn't possible to do as a plugin?

[rwols]

I'm not saying it's impossible, but likely it's going to be an uphill battle until there's a dedicated API for this in ST.

See: sublimehq/sublime_text#817

[pushqrdx]

@rwols yeah the workaround presented seems pretty ineffecient too. Did you try to directly ask the developers at discord? maybe they will consider adding a facility for region highlighting in ST 4

[predragnikolic]

This issue can be closed now.

[rchl]

If so then I guess we need a more specific issue for tracking upstream support as current solution has many drawbacks.

[predragnikolic]

I am subscribed to that issue at sublimehq/sublime_text#817

But yeah, if people start complaining about error underlines not being visible, due to semantic highlighting regions being drown on top of error regions, and vice versa, than yes. An issue for that will probably exist.