Refusal to support LSP extensions leads to basic unusability #11730
Unanswered
workingjubilee
asked this question in
General
Replies: 1 comment
-
We discussed this in the Matrix space. For this case it might be enough to support the
Also updated the FAQ to document the intended policy for LSP extensions in the future: https://github.com/helix-editor/helix/wiki/FAQ#are-lsp-extensions-supported |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
Because the LSP protocol does not provide, in its base protocol, information sufficient to inform the user of things like "the server is crashing on failure to build", an LSP extension must be used to do this. Because Helix refuses to support any extensions, this leads to Helix lacking basic functionality: the knowledge that an extension is thrashing on a useless activity, wasting compute time and silently not informing me of why the LSP feedback is effectively dead.
It does not matter if something is an LSP "extension" if it leads to the program failing to do its one remaining task when it is a nonworking program of requesting human intervention instead of silently dying. If you do not want to support any extensions whatsoever, then consider ceasing to support LSP, because the protocol requires extensions in order to have basic functionality.
Reproduction Steps
I tried this:
helix pgrx/src/callconv.rs
I expected this to happen: Helix propagated the build errors.
Instead, this happened: Helix failed to provide basic information.
Helix log
how many lines do you want of the same output, I mean it's just tons more of this:
~/.cache/helix/helix.log
Platform
Linux
Terminal Emulator
konsole 24.05.1
Installation Method
pacman
Helix Version
helix 24.3
Beta Was this translation helpful? Give feedback.
All reactions