Closed NickeZ closed 7 years ago
The line in diff is used only by neovim-completion-manager, not related to deoplete at all. (Also the oneline log.)
If you need to see all the messages between language server, change https://github.com/autozimu/LanguageClient-neovim/blob/master/rplugin/python3/LanguageClient/logger.py#L10 to logger.setLevel(logging.DEBUG)
.
One more thing, deoplete and neovim-completion-manager might not work well when both turned on.
The information provided is too limited. If you need more help from me, please provide minimal vimrc, test project, complete log and reproduction steps.
I was switching back and forth trying both, so you mean that I might have had some NCM stuff still around when I was testing deoplete? I'll try some more. I kind of assumed that cm#register
was a convention among completion managers and that all implemented that function.
They use different approaches.
When you have deoplete installed, it will try pick source from this plugin.
For neovim-completion-manager though, this plugin will always try register itself as a source. Obviously, when the neovim-completion-manger is not available, it will fail and generate a warning, which can be ignored if you don't use neovim-completion-manger.
Any updates regarding this?
I'd like to close this if it has been resolved or not relevant anymore.
Closing as lack of response.
When I try to use LanguageClient with deoplete it doesn't work. I looked into the code and made a small diff but I can't troubleshoot it any further becuase I don't really know any details. It works fine with NCM.
I use latest master of both plugins. CheckHealth reports that everything is fine.