-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not compatible with Oni #262
Comments
Hm. It is not dein problem. |
If oni can tell dein the GUI client name. |
I think you should not share the dein cache directory between normal neovim and Oni. |
Hmm... It looks like in Oni |
If plugin can check neovim |
Oni uses |
dein should check runtimepath in cache loading. |
Thank you very much! The fix works great! |
Problems summary
Dein is not compatible with Oni because of the caching of
runtimepath
.dein#load_state()
overwrites the entireruntimepath
, which also contains the runtime paths added by Oni, which are essential for Oni to behave correctly. If I runnvim
once before runningoni
, then theruntimepath
will be overwritten to theruntimepath
when I previously runnvim
, and that causes problems in Oni.Expected
There should be some mechanisms to deal with such problems, as many GUIs may add their own
runtimepath
s. But I cannot imagine a good way to solve this at the moment.Environment Information (Required!)
Provide a minimal .vimrc with less than 50 lines (Required!)
The reproduce ways from Vim starting (Required!)
There must be
"oni.loadInitVim": true
in Oni's config (~/.oni/config.js).Method 1:
nvim
.:q
to exit, but I cannot figure out what setting caused that. But if I calldein#clear_state()
and restart Oni, it works with no problem.)Method 2:
nvim
.nvim
, you should see nvim continuously reportsno notification handler registered for "oni_plugin_notify"
error. That is because Dein has loaded theruntimepath
cache when using Oni before, which does not work innvim
.Screen shot (if possible)
Upload the log messages by
:redir
and:message
(if errored)The text was updated successfully, but these errors were encountered: