Replies: 1 comment 1 reply
-
What's the buffer text LSP? You mistakenly hyperlinked to the snippet LSP. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I’ve been using multiple LSPs for a while and it’s really useful. I can get autocompletion from buffer text, snippets and co-pilot in addition to the language specific LSP 🥳
However there are couple of improvements that I’ve noticed
Here are the ones that I couldn’t find an existing issue or discussion:
Completion popup is shown when all LSPs respond with completion items. This means that the delay for showing the popup is determined by the slowest LSP. For me this is almost always co-pilot which does network request(s), thus sometimes takes multiple seconds to provide a completion. It would be nice if the completion popup is shown when the first LSP responds and completions are added when subsequent LSPs provide their completions.
Like mentioned, I use quite many LSPs (buffer completion, snippets, co-pilot) for practically all the languages. I have to configure these LSPs manually to every language in
languages.toml
. An option to define a global LSP that will be used for every type of file would be useful for this kind of use cases.Completion and code actions popup don’t show which LSP provided the item. It would be ideal to show name or, even better, configurable abbreviation for the LSP.
Modify start/stop/restart LSP commands in a way that it would be possible to specify which LSP to target with the command.
These have existing issues/PRs, and I think they would be useful:
Beta Was this translation helpful? Give feedback.
All reactions