Closed aceforeverd closed 1 year ago
lazy.nvim
is plugin manager and dein.vim
is also plugin manager.
You must not mix them together. It will conflict.
I'm not sure it is dein or lazy, but it seems fail only if the two together.
Why do you mix them? Please describe. I think it is not needed.
I'm not sure it is dein or lazy, but it seems fail only if the two together.
Why do you mix them? Please describe. I think it is not needed.
I share common plugins of vim & neovim with dein historically, goes fine before 0.9.0
I share common plugins of vim & neovim with dein historically, goes fine before 0.9.0
It may work older neovim. But it is not supported behavior. dein.vim works both Vim and neovim. What is the problem?
I share common plugins of vim & neovim with dein historically, goes fine before 0.9.0
It may work older neovim. But it is not supported behavior. dein.vim works both Vim and neovim. What is the problem?
Thanks. Just trying things in my comfortable way, will move forward.
I think you want to manage Vim plugins by dein.vim
and neovim(lua) plugins by lazy.nvim
.
It should not.
dein.vim can manage Vim plugins and neovim plugins.
Related Issues
Not found yet
Description
Lua stack overflow error if setup together with lazy.nvim.
Here is the message:
I'm not sure it is dein or lazy, but it seems fail only if the two together.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Desktop:
Minimal Config
Additional context
Add any other context about the problem here.