Closed dmitmel closed 2 years ago
Nice, thank you! Does it look possible to add a test?
Dunno, I don't see any tests involving plugin classes or similar. Plus this bug is just a one-off typo to me.
Sorry for bumping this PR, but what are the chances of getting a bugfix release soon? I need this for a plugin I am writing currently. It's not urgent, but I would rather avoid following HEAD
for just one plugin.
As a workaround you can just post some dummy notification/request to the remote plugin when Vim loads. An empty method on the Python side is enough.
I know, I already am doing that, so it's not a big deal, just ugly. (I am making a plugin which reads in the linter settings from pycodestyle and returns a dictionary, so I can set my Python file type settings automatically to match the linter settings)
A kind bump-up: pynvim v0.5.x (or any new version that includes this fix) is still unreleased.
I think @bfredl is required for that currently :)
What PyPI username should I add to the package?
"nvim" ? what was it before?
This happens only right after instantiation of the plugin class, so calling any other asynchronous function seemingly fixes the problem.
Fixes #434.