You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since (as given by VSCode as example) textMate Grammars seem to be a defacto standard for doing token/grammar based highlighting we have a "thing" in lsp that prevents us from language servers beeing self contained. we always need a side channel to provide the text mate grammars as vscode does it through the configuration in package.json.
it would be nice to have a service in the protocol that allows the servers to deliver the grammars to the client or alternatively a service that does grammar based highlighting server side.
The text was updated successfully, but these errors were encountered:
Thanks @svenefftinge. It is a dup of #7. I think if we open up the protocol for sematic classification then we can also support syntax classification. However syntax classification has the pre-requisite that it has to be fast and accurate during typing. So this must be defined in a clever way.
Dups #7 and #18. Lets continue the discussion in #18.
Since (as given by VSCode as example) textMate Grammars seem to be a defacto standard for doing token/grammar based highlighting we have a "thing" in lsp that prevents us from language servers beeing self contained. we always need a side channel to provide the text mate grammars as vscode does it through the configuration in package.json.
it would be nice to have a service in the protocol that allows the servers to deliver the grammars to the client or alternatively a service that does grammar based highlighting server side.
The text was updated successfully, but these errors were encountered: