fredizzimo
fredizzimo
@damanis, I mean the code in neovim-qt waits a half second for neovim to quit and then gives up. We need to know if it exits because of the timeout...
I managed to reproduce the issue now, and reported a neovim bug * https://github.com/neovim/neovim/issues/26743
I still think that neovim-qt forcefully closes Neovim if it's not responding. The rpcrequest, vs notify does not apply here, since our own clipboard integration is not in use unless...
@damanis, did you also close stdout? Both needs to be closed. Also make sure that you are using xsel, and not xclip Neovim already closes stdout for xclip, so only...
Strange, it worked for me, but I'm not sure if I tested the workaround for xsel, only xclip, so there could be a difference there. Are you, sure that you...
This might "fix" the issue due to neovide no longer waiting for neovim to exit * https://github.com/neovide/neovide/pull/2265 But it might cause an almost equally bad issue of leaving Neovim running...
This is fixed in Neovim 0.10.0 and since our new 0.13.0 release requires that, I'm closing this issue.
I can confirm that I see the same problem. If I use `LXGW WenKai` as a fallback font the spacing is wrong, but if it's the primary font then everything...
@Parsifa1, I'm sorry, I did not have time to work on this yet. And probably won't for around 3 weeks. But if someone else wants to try to fix it,...
We, don't need much additional support from Neovim for this. I will try to send a PR to them soon with the support we need, so it gets included in...