Closed andrius closed 5 years ago
Hi @andrius, thanks for the report. My latest commit 41d166a checks if CompleteChanged
event exists (supported only on nvim nightly and vim v8.1.1138), should fix this issue. Let me know!
Works, but now I had to do make upgrade
and make update
and few times :UpdateRemotePlugins
. But it worth so, nvim looks fantastic! Thank you!
:UpdateRemotePlugins
, it ignores lazy-loaded plugins (via dein), so you better run: :call dein#remote_plugins()
which will take into account the lazy ones.:call dein#clear_state()
and after the next you start n/vim, the state will rebuild.local.plugins.yaml
, you'll eventually need to run :call dein#recache_runtimepath()
for dein to re-merge all the plugin essentials. Run it with a fresh state.See #117 for a new feature to disable or overwrite plugin configurations.
Let me know if you're cool.
I just made a try and still getting errors with neovim. Host machine: Debian 9.7 with homebrew installed
Case 1
When I starting vim and trying to edit files, I get this:
Case 2
No errors, but any popus does not working, ctags etc too. Just getting fancy looking nvim