@equalsraf
@equalsraf
It seems this only happens when using a symlink to the actual binary, like the example in the neovim wiki.
Not really, does it work in the console Vim?
Sorry guys, I dropped off the face of the earth for the past year. The issue seems similar to one we saw in the [early days of Qt5](https://bitbucket.org/equalsraf/vim-qt/issues/56/port-vim-qt-to-qt5#comment-23381299) where QWidget::scroll...
The notifications come from nvim-qt but the messages themselves come from pynvim https://github.com/neovim/pynvim/blob/f9e56f8ef2a0d93da4ad1c64e82066be77ecde64/neovim/plugin/host.py#L110 You can verify this by disabling all python plugins. FWIW I'm planning to change the vimscript in...
Cheers, two cents We cant generically use the msgpack type STR in all returned values yet - because we cannot guarantee the encoding of the strings (e.g previously in #1130)....
> So, the encoding (including binary or so) has to be known on the other side - which should be possible, as reading a "line" from a buffer can be...
@phmarek I agree, that lint is a bit too pedantic - basically thread safety for the sake of it, and rand_r does not ensure thread safety, only that it is...
What about the str encoding?
Now that I look at it where msgpack_rpc_error being used?
In any case `msgpack_rpc_from_string()` as STR is probably out. > Still, sending error messages as byte-stream just because a filename (or other part) might not be valid UTF-8 sounds wrong...