Closed ashfinal closed 2 years ago
Sorry, I wasn't exactly active recently and by now nvr.py
has diverged quite a bit.
If you're still interested in solving this, it's probaby easier by now to just reopen multiple small PRs that are easier to review, since I don't want to spend much time on this project.
Otherwise I'll try to cherrypick your commits (although I can't really check for Win compatibility).
Sorry for the late reply.
Yeah, I'm still interested. I don't use Windows much nowadays, but I do have a dual-boot machine. Just need some time to refresh my memory...
I will try to create some mergeable pr in today or tomorrow.
follow-up #177
These patches are based on lastest commit 1ec7c6c76a66d8d381f54570d6fdd3079c190ba5, an compilation of #135 and #136. The changes include:
Use multiprocessing module for Windows platform compatibility, i.e. neovim-remote now should work flawlessly on *nix systems and Windows.
Fixed
--serverlist
option.--serverlist
arg didn't work on Windows, this fixed it.Also produce
gnvr
binary for GUI use. If you want to add "Edit with Neovim" to right click menu, this is your thing. Your Windows registry entry should look like this:Nvr can lauch multiple neovim instances now. By default, nvr uses the address
127.0.0.1::6789
on Windows while/tmp/nvimsocket
on *nix systems. But if you explicitly designate a valid--servername
option, nvr will help start another neovim instance, unless--nostart
option is included simultaneously.Other minor fixes. Please refer to commit messages if you are interested.
@mhinz Please merge this PR instead, now it should have no conflict. If anyone want to try this, plesse clone this repo, checkout the
win_platform
branch, then typepython setup.py install
on your Windows prompt.