-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
LSP client does not send initialized
notification
#2295
Comments
Sounds plausible, thanks. (Though I have long since switched to a different client, for this and other reasons) |
Looks like there's a function |
Okay, finally this makes sense. The are two messages in the protocol, one is I can fix this over the next few days. |
Exactly. Found using |
What's annoying is that this bug was hard to catch, because most servers don't follow the spec and work even if you don't send |
Okay, I should have fixed this now. Try it out. |
I can't confirm that it works. |
Cool, thank you for reporting the issue. It helped me finally figure out what was wrong. |
Umm, it still doesn't work for me, but I don't have an easy way to sniff the server-client communication to be certain. |
Oh, you "can't confirm." Sorry, I read that as "I can confirm." |
Which language server are you testing this with? I can confirm that the |
I've tested it with
|
The function isn't defined in NeoVim, you'll have to test this with Vim instead. |
See this NeoVim issue where I requested that they implement something similar: neovim/neovim#9010 The only way to log channel messages at the moment in NeoVim is to compile NeoVim differently. |
I think they plan on implementing a similar function eventually. |
I could try, but it might take a while until I find time to set up Vim. |
Cool, let me know how it goes. |
If you want to try that language server, use |
|
That's very strange. The message is sent, and then the server says it isn't. I bet it's expecting an empty object to be sent in |
Okay, |
Yeah, that works, thanks. |
Nice! Thank you for your help with testing this. |
...as of e882436.
Possibly related to #1786.
cc @dimbleby
The text was updated successfully, but these errors were encountered: