WIP: basic coroutine and subprocess support #393
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work towards #342
The model supported here is: plugin code is written as greenlets ( spawned as request handlers or
nvim.async_call
), but once in a while needs to invoke a coroutine defined by some library (such as asyncio itself). This model is enough is to use the io facilities of asyncio, which mostly uses raw callbacks.nvim.run_coroutine(coro)
will spawn an asyncio task and suspend the current greenlet until completion and return the result. If you don't care about the result you can still use the non-blockingasyncio.ensure_future(coro)
.A simple example to suspend the current handler for some time (NB: will block nvim if the handler is
sync
):As a convenience a wrapper for the subprocess protocol is also added, which wraps the data handler in a greenlet (so that it can use
nvim
requests):