-
Notifications
You must be signed in to change notification settings - Fork 27.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kickstart calls kickstart-lsp-highlight
augroup regardless of support
#899
Comments
Ooh. This is interesting. Thanks for the report! Would you be willing to take a look around at other people's configurations to see how they might properly support this use case? |
I'm not familiar, and not very involved in the community, so that would be difficult, but I'll have a look But it should easy to check if the group exists and just not run it then, right? I'll look into this a bit later and open a PR if that is fine Or just move the group creation up? In case a plugin also relies on the existence of the group |
That would be amazing! For an honest to god functionality breaking issue like this I and I'm sure others would be happy to help whip it into shape if the first go around isn't perfect. Thanks so much for being willing to contribute, and thanks again for the report! |
@dam9000 The more the merrier :) |
Actually just noticed that it's a bit worse than I had assumed, this also occurs if the LSP crashes, i.e. |
Let's give @sudo-tee a couple days to respond, and if it's radio silence we can revert that PR if necessary. Obviously if anyone has any better ideas that would fix all the use cases I'm definitely up for that too :) |
Describe the bug
Kickstart registers a autocmd for
LspDetach
, which calls the augroupkickstart-lsp-highlight
, but if the server does not support the capabilitydocumentHighlightProvider
, this augroup does not exist. The following error is thrown:To Reproduce
Desktop
Linux <cut> 6.5.0-28-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 28 23:46:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Neovim Version
The text was updated successfully, but these errors were encountered: