Steven Trotter

I've hit this problem too with this plugin, it seems it's really an issue on Neovim to me, I've looked into it a bit and found that the problem is...

> > Can be triggered by just doing this with a relatively recent version of Neovim: > > > echo -e -n '\x94\x00\x0a' | ./build/bin/nvim --embed > > Even that...

Literally hit straight away on latest version of Neovim on master: ``` strotter:neovim$ make distclean rm -rf .deps build make clean make[1]: Leaving directory '/home/strotter/code/nvim/neovim' strotter:neovim$ git status On branch...

In fact it seems to trigger on anything that it doesn't see as valid msgpack, which is not completely unreasonable, except in the case that it's incomplete msgpack that's just...

Sorry just seen this, I'll try and look properly tomorrow again but I think just on my Rust based nvim plugin: https://github.com/strottos/nvim-vadre The plugin is basically a step through debugger...

A lot of your conclusions looked similar to mine. The linked PRs did nothing to fix this and after a day or two of trying to figure out a fix...

Seems to work for me now on first test, and this was really something that was happening constantly before for my plugin.

Thanks for all your hard work on this @KillTheMule , really is appreciated 👏

I would strongly support this, I realise this is an old issue request now and maybe this repo isn't being maintained. The workarounds suggested don't *always* work, if something isn't...