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
LSP version: Version: 0.12.1, commit 1928d88ff8bc3e178ad098146bec252751383a48 (Typst version 0.10.0)
OS version and name: Arch Linux, up to date
✅ I am on the latest stable version of the extension/LSP.
✅ I have searched the issues of this repo and believe that this is not a duplicate.
Issue
Typst-lsp does not give any responses at all after receiving an early workspace/didChangeConfiguration notification, though the "settings" param is empty. This causes it fail to work with Emacs's eglot. I have asked eglot's developer: joaotavora/eglot#1363 and they thought it's server's bug.
As long as I configure the client not to send workspace/didChangeConfiguration after connection, the server would work properly.
The above eglot issue contains a minimal recipe of reproduction steps.
Note there are many "timed-out request" message near the bottom of the log, and that the workspace/didChangeConfiguration notification is sent to server before server registers this capability.
The text was updated successfully, but these errors were encountered:
Issue
Typst-lsp does not give any responses at all after receiving an early
workspace/didChangeConfiguration
notification, though the"settings"
param is empty. This causes it fail to work with Emacs's eglot. I have asked eglot's developer: joaotavora/eglot#1363 and they thought it's server's bug.As long as I configure the client not to send
workspace/didChangeConfiguration
after connection, the server would work properly.The above eglot issue contains a minimal recipe of reproduction steps.
Logs
https://gist.github.com/Zjl37/d506c225bce175e584a78d47e0dbecab
Note there are many "timed-out request" message near the bottom of the log, and that the
workspace/didChangeConfiguration
notification is sent to server before server registers this capability.The text was updated successfully, but these errors were encountered: