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
You may also try reproduce the issue using clean environment using the following command: M-x lsp-start-plain
Bug description
Responses sent by a language server containing {} are interpreted as null. When interpreting the capabilities field of the initialize response, this causes lsp-mode to think that a capability is not supported when it actually is.
In my own use case, the language server is responding with the following:
lsp-mode interprets the value under the completionProvider field as null, which prevents lsp-mode from asking the language server for completion suggestions.
Steps to reproduce
Follow these steps to use plists for deserialization.
Use a language server that sends back a {} in its initialization response.
Set lsp-log-io to t.
Start the language server via lsp-mode.
Use lsp-workspace-show-log to show the log.
Inspect the initialize response and confirm that a null appears instead of {}.
Expected behavior
Rather than null appearing, the io log should show {}. This is the case when lsp-use-plists is nil.
Which Language Server did you use?
This happens when using tabby-agent. The language server's initialize response is:
Thank you for the bug report
lsp-mode
related packages.M-x lsp-start-plain
Bug description
Responses sent by a language server containing
{}
are interpreted asnull
. When interpreting thecapabilities
field of theinitialize
response, this causeslsp-mode
to think that a capability is not supported when it actually is.In my own use case, the language server is responding with the following:
lsp-mode interprets the value under the
completionProvider
field asnull
, which prevents lsp-mode from asking the language server for completion suggestions.Steps to reproduce
{}
in its initialization response.lsp-log-io
tot
.lsp-workspace-show-log
to show the log.initialize
response and confirm that anull
appears instead of{}
.Expected behavior
Rather than
null
appearing, the io log should show{}
. This is the case whenlsp-use-plists
isnil
.Which Language Server did you use?
This happens when using tabby-agent. The language server's
initialize
response is:OS
MacOS
Error callstack
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: