bfredl

What happens if the method calls a blocking nvim method ( i e `nvim.eval('1+1')`) after an `await` ?

Peek is the most general API, as `try_next_message` (`next_message(block=False)` ?) could be implemented as ``` if nvim.peek_message(): msg = nvim.next_message() # do stuff with msg ``` but of course we...

The most scalable way to integrate multiple event sources and yieldable workers is to use the event loop `nvim.run_loop(request_cb, notification_cb, setup_cb)` and not `nvim.next_message`. It implements a gevent-like interface, also...

Literally mixing with gevent code will likely never work, what I meant is that it implements a gevent-like abstraction: you typically don't need to suspend and resume greenlets yourself, rather,...

I _think_ you can, but you must have then created different `nvim` objects by multiple `neovim.attach` calls, and then always use the correct `nvim` instance in each loop.

The behavior is expected as long as one is aware that it is an rpc interface; the problem is the that it is so well integrated that one often does...

It was likely an error that stopped the plugin from loading. This error should be echoed now (so it can be fixed)

Ah, sorry read the description too quickly, seems the `\` is lost along the way (likely an issue with the neovim rplugin host logic and not python-client specifically)

It can't work, as ftm the host only checks for handlers at startup. For now you need to define it as a `function` directly in the class and use `vim.command("autocmd...

it might be a bit inconvenient, but a plugin shouldn't do stuff that has an effect on nvim in `__init__` as the plugin has no control when init is run....