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
The LSP specification says that LocationLink[] support should depend on the client capability textDocument.definition.linkSupport, but the server doesn't appear to actually do this.
This issue came up recently with eglot, a client for emacs, here: joaotavora/eglot#711
There is an example in the linked issue. The version of lua-language-server used there is 2.3.1.
The text was updated successfully, but these errors were encountered:
This extension was originally designed for VSCode, so I only guarantee its compatibility with VSCode.
For most of the functions, I did not check whether the client provides this capability, but simply assumed that it does.
Because it takes too much time and energy to check every capability and correctly handle the behavior when the capability is missing, especially for individual developers like me.
However, as more and more language clients appeared, I also added many compatibility measures based on feedback. If you find a new compatibility issue in the future, you are welcome to continue to give feedback and I will try my best to solve it.
Sounds quite reasonable. That said, I would expect to see more non-vscode usage (and possibly bug reports) in the future as this server seems to have become the de facto default language server for lua, and is increasing in exposure. For example, it was added to the arch linux [community] repository last week.
By the way, thank you very much for creating lua-language-server. My experience using lua has been much better since I started using it.
The LSP specification says that
LocationLink[]
support should depend on the client capabilitytextDocument.definition.linkSupport
, but the server doesn't appear to actually do this.This issue came up recently with eglot, a client for emacs, here: joaotavora/eglot#711
There is an example in the linked issue. The version of lua-language-server used there is 2.3.1.
The text was updated successfully, but these errors were encountered: