Replies: 2 comments
-
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'd probably like to bump this. Especially now with nvim 0.11 lsp upgrades. I've removed lspconfig from my config, but I can't use neoconf anymore due to it crashing without lspconfig. And that despite having disabled all lspconfig/lsp specific config options as well. I think this plugin could really benefit from not being tied to lspconfig |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Neoconf seems to set itself as a configuration manager of lsp server. Therefore, it requires lspconfig plugin.
But is it possible to use it as a general configuration manager for non-lsp plugins?
If we target it as a general configuration manager(manager for both lsp&non-lsp plugins), then it's kind of weird that neoconf will crash without installing lspconfig first.
Beta Was this translation helpful? Give feedback.
All reactions