-
Notifications
You must be signed in to change notification settings - Fork 4
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
xmlrpc ResponseError #22
Comments
I've tried installing dokuvimki on another machine that's just had a fresh OS install but get a different yet similar error:
Running nvim v-.5.0-dev+941-g9c56d8e5f Steps:
Insert into ~/.local/share/nvim/site/pack/alazyDokuVimKi.vim
Insert into ~/.config/nvim/init.vim
I'm relying on neovim/vim8 native plugin management and am using python3, but I think that should still work. Would you be able to pass on any XML-RPC Error Codes so one can have some idea of what's wrong? xmlrpc isn't totally dead. I'm taking some agonizingly slow baby steps to figure this out but |
Yes, if Vim is built with Python 3 support, that is used. Otherwise Python 2. I've just tried NeoVim and it seems to be working for me:
I think the URL in your Vim config may be wrong. I should be the root of your wiki, since Can you try setting it to the same URL you used when you tried via
|
I just tried appending
If I disable error handling in
|
@alazyworkaholic is this still an issue for you? |
@alazyworkaholic any update? |
After leaving Dokuvimki aside for several months I fired it up again and found it won't start. Unfortunately, I don't remember at all what I might have done to the computer during that busy time that caused this issue. Dokuwiki itself continutes to run perfectly well through the browser.
Ubuntu 20.04 x64
Upon starting nvim and running DokuVimKi.
So I try a health check:
I see the python 2 error that msgpack and pynvim are missing but I think it's irrelevant because DokuVimKi should (I think) use python3, which doesn't show any checkhealth error.
How can I find out what's gone wrong with the xmlrpc response handling?
The text was updated successfully, but these errors were encountered: