-
Notifications
You must be signed in to change notification settings - Fork 28
Could not find neovim #3
Comments
Sorry for the late reply Does your vim If so, this plugin will choose pythonx ( |
My vim does not have |
If you can't do |
I could do |
Use this command to set environment variable and start your nvim/vim8
After you see If there's no log file, then you have to try start NCM manually, and see what's happaning,
|
I reinstalled vim with python3 supporting. It works fine now. Thanks for your help! |
Hi! I'm having a similar issue... I'm using vim8 and I have the same configuration on my Mac and my ArchLinux machines.
My vim8 has support for python and python3, and this is the log when I run:
And some outpus: When I open vim
:python import neovim
:pythonx import neovim
:python3 import neovim works :pythonx import neovim_rpc_server
:python3 import neovim_rpc_server works! :echo globpath(&rtp,'pythonx/neovim_rpc_server.py',1)
:echo neovim_rpc#serveraddr()
I think that's the problem, it can't get the proper RPC server address. Any help? Thank you in advance, |
This plugin choose In your case, you need to ensure As an alternative, you could try add |
Thanks, @roxma! Thanks, again |
|
@stevenmwade |
Having a similar issue on Arch, running
But running This lead me to this issue over at After running Hope this helps anyone else running into this problem 😄 |
@kepbod It works for me. However, because the default of pythonx is python2: so have to add: if has('python3')
set pyx=3
else
set pyx=2
endif to .vimrc |
Hello everyone, This is what happens when I start vim8.
I tried 'set pyxversion=3' in my .vimrc but I still have the same issue.
Any idea ? |
I have same error, @MatarC. 😄 |
@MatarC Hi, 😄 I upgrade my vim by Homebrew and It's working fine now ! The error may caused by you upgraded your python but don't re-compile your vim! |
@UzimakiNaruto seems to work thanks! |
@krak3n I remember this solution worked for me last time, however, now I'm on Python 3.7 and I can no longer downgrade and install greenlet 0.4.10. Are you having any problems after updating Arch? |
@terminalproteus I just ran into this today. I'm running Antergos so I dunno for vanilla Arch but I just pip uninstalled neovim, greenlet and msgpack and installed from the repo's instead and it seems to work. |
Just installed |
I have the same problem with vim 8.1. I do not know what the culprit is, but I must have happened in the last month or so when I updated my system. I currently run on debian/sid and all the above did not work for me :-(
On the terminal I can do: But If I do the same in vim like: So, why can I import neovim from the terminal, but not from within vim? |
You should reinstall python neovim package. |
@Shougo What do you mean? Isn't |
If so, you should check what python is used in neovim. |
Oh it is Vim8. I recommend for you to set g:python3_host_prog. |
No, sorry. does not change a thing ;-( |
g:python3_host_prog only affect for vim-hug-neovim-rpc. You should set pythonthreedll option. |
Oh I have found you use Debian sid. But your neovim module is installed in Python3.6 directory. |
@Shougo First of all, thanks for your help. I definitely appreciate it! Here's what
|
I don't know why it does not work in your environment. I think you should rebuild your Vim to the latest version. |
And you should test vim-hug-neovim-rpc in othe environment. |
Yes, indeed. I went back in history. Up to this one, everything works fine: https://snapshot.debian.org/package/vim/2%3A8.1.0320-1/#vim-gtk3_2:3a:8.1.0320-1 But after that, the problems popped up. I'll contact the maintainer of the package. Thanks for all your help! |
@Wir3 and to anyone else who is having issues downgrading to greenlet-0.4.10 while on python-3.7, I think it's a bug with cython being incompatible with python-3.7. You'll have to do what I did and first uninstall the current version of greenlet with
Before running
Finally you can run |
I also found, that |
I have installed neovim via
pip install neovim
, and in vim the command:python import neovim
has no errors. However, when I opened the vim, it reported thatNo module named 'neovim'
.The text was updated successfully, but these errors were encountered: