fredizzimo
fredizzimo
Hm, that appears to be different then. But we do have a similar issue on Windows, without the clipboard involved. * https://github.com/neovide/neovide/issues/2182 Do you have a logfile?
I see what's wrong, since we handle neovide ui draw commands and other messages separately, we can receice a draw command after the quit confirmation. This changed the events to...
Actually, it could also be the same issue as on windows, that the neovim handler never quits.
I'm closing this in favor of https://github.com/neovide/neovide/issues/2182, which have more information. If you still have problems with the latest 0.13.1 release on Windows, please reply there along with your system...
The `DecodeError` seem to indicate that it's Neovim that crashes first. It's similar to this bug https://github.com/neovide/neovide/issues/2166, but that only crashes with some very specific steps. Could you check with...
From the callstack it looks like you have some plugin that calls `vim.iconv` with an invalid string. Maybe you could do a grep in your plugin folder to see what...
Based on a Github search, it's most likely `gitsigns`, and less likely `telescope`. But `telescope` does not match the symptoms.
@AstraLuma, could you try to disable `gitsigns` to confirm that's causing the problems? And if that's the case, open a new issue on the `gitsigns' repository?
Did you ever find out the cause?
Closing due to lack of response.