-
-
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
Problem launching server on Neovim #28
Comments
The child process used for doing the pathfinding has not launched, or not connected yet, hence How soon did this occur after starting Vim? Perhaps it just hadn't started up fast enough to be ready to receive requests. Adding a check for that situation and displaying a better error message (or waiting for the server to load) would be a good idea, I'll do that soon. |
I just pushed some changes, could you update to at least d58490b and let me know what happens then? |
Okay, new error this time
|
#28 suggests that some people may have been trying to install these as Python libraries.
Are you using Neovim? If you are I think I know the problem. |
I am using neovim... :D |
Yeah, that's probably it then, I'll push a hopeful fix in a minute |
Ok can you try it with d72b386? I can't test since I only have regular Vim/GVim installed |
No luck, I'm afraid, thank you for your effort though! |
I think we need to add something to fetch and log stdout/stderr from the child process so that we can see what has gone wrong. |
I have the latest
python3
and did apip3 install
fortimers
andpopupwin
The text was updated successfully, but these errors were encountered: