bfredl

Almost there: ``` python -m nose 72 .............................E....................... 73 ====================================================================== 74 ERROR: test_vim.test_command 75 ---------------------------------------------------------------------- 76 Traceback (most recent call last): 77 File "C:\Python35\lib\site-packages\nose\case.py", line 198, in runTest 78 self.test(*self.arg)...

Sorry been busy with other stuff. Just made the second attempt of asyncio on windows, let's see if appveyor likes it...

Later on we might want abstractions directly in the API for regions on the character-level, especially with extmarks that care about adjusting character position. At first API functions that gets...

Maybe just add it to the ignore list in setup.cfg

Hmm, this only prints the exception message, not the exception typename, maybe we want "{}: {}" with args `type(exc).__name__, exc`. But it seems also `v:exception` problem in general, consider (in...

I forgot to push the last fix. I also fixed stdin capability: `start_subprocess` returns transport with `.write()` method.

> The sleep works, but in subprocess cannot access neovim until RPC is finished. @Shougo What is the situation more specifically? If the parent python process is in a sync...

The subprocess can use nvim, but for now it has to connect on its own using `$NVIM_LISTEN_ADDRESS`. I don't think a socket handle can be duplicated in a portable way...

This is a bit tricky, parent and child python cannot collectively "own" the nvim focus, only one channel can be blocking at a time. For now it has to be...

nvim-managed greenlets and asyncio coroutines are like water and oil, they are incompatible event/async primitives that simply don't mix: any attempt to "seamlessly" integrate them might fail in the first...