-
Notifications
You must be signed in to change notification settings - Fork 35
Failed to launch Coq in wsl #245
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
Comments
Thanks for reporting. Could you try adding |
It says Also, I tried doing the samething with neovim 0.7, and coqtail was able to start successfully. So I guess it has to do with the vim version I was using. I don't know what configuration causes it to break, though. |
It seems like there may be something wrong with the Vim-Python channel. Could you try |
==== start log session ==== |
Maybe coc is interfering somehow? What happens if you disable that plugin? |
==== start log session ==== |
Ok, so coc seems unrelated. Vim is successfully sending a message to Python, but it's not receiving the response. Try adding try:
ret = handler(**args) if handler is not None else None
msg = [self.msg_id, {"buf": self.bnum, "ret": ret}]
print(msg)
self.wfile.write(_to_jsonl(msg))
except (EOFError, ConnectionError) as e:
print(str(e))
break |
I got this: [1, {'buf': 1, 'ret': ({'version': (8, 13, 2), 'str_version': '8.13.2', 'latest': None}, '')}] |
So it looks like the Python side is sending the response, it's just never received for some reason. Thanks for your help so far but it looks like I'll probably need to do some debugging on my Windows machine, which unfortunately I won't have access to for a few weeks. In the meantime if neovim works I'd suggest sticking with that for now. Feel free to keep digging into this if you're interested, but I don't have any ideas at the moment for an obvious next place to look. |
I finally got around to trying this on WSL and unfortunately I'm not able to reproduce it. So I think I'm stuck unless someone else runs into this and we can get more information about what's going on. |
After resolving #316 , I saw this issue. In my case, I was able to resolve it. I had set the
Seeing the welcome message surprised me. Removing it altogether (because coq is in the path) resolved it for me, anyway. |
I am having trouble starting coqtail in vim under Windows WSL2.
When I execute
:CoqStart
with debugging information enbaled, I getFailed to launch Coq.
Here is the log information I get
The text was updated successfully, but these errors were encountered: