Open gabysbrain opened 2 years ago
I have the same issue with a similar config, have you found a fix yet?
Nope, I can't use this plugin until it's fixed unfortunuately.
On Fri, Dec 03, 2021 at 12:14:05AM -0800, scrouthtv wrote:
I have the same issue with a similar config, have you found a fix yet?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.*
Sorry for neglecting to get to this for so long. I've been unable to reproduce this issue with your config - do you see this error with servers other than JuliaLS, or just that server?
Also, if you're willing to help debug this, could you please try putting print
calls with unique messages at the calls to util.ensure_init
in lsp_status.messaging.register_client
and lsp_status.messaging.progress_callback
, so that we can narrow down where the nil
value is occurring?
I'm also not able to reproduce this issue anymore. I tried some things in my config, I guess the order in which plugins are loaded is relevant. The plugin is currently working for me.
yes, it's working for me too now! lightline doesn't seem to support animations but that's fine.
I tried setting up lsp-status according to the example config in the readme but once my lsp loads I get an error (also see https://github.com/nvim-lua/lsp-status.nvim/issues/9#issuecomment-913260530 who seems to be having the same issue):
My lsp/lsp-status config is here. It's basically the lsp-status config from the readme but integrated into the default config from lspconfig.
From looking at the lsp-status source my guess is that
id
is never set but I can't figure out why.