fredizzimo

In Neovide we also still have some reports of crashes. Here's one including a log file from the Neovim side * https://github.com/neovide/neovide/issues/2437#issuecomment-2105690743 Based on a very surface level analysis it...

I also believe that the fix by @theofabilous, was just a band-aid fix on the receiving side, while the actual problem occurs on the sending side. * https://github.com/neovim/neovim/pull/28355

> No, it is not. Just out of curiosity, what does it fix, other than optimize things, did someone report performance problems? Reverting something just before a release that has...

> ?? details that identifies **this particular crash** was reported one hour ago, not two months ago. We will not revert a lot of work in a panic before anyone...

The problem is that this causes a lot of crashes together with Neovide, so it very much affects us too. And I think the reports we have got this far...

The 0.9.5 series is not stable either btw, since https://github.com/neovim/neovim/pull/27348 was never backported. So our current suggestion is to build Neovim from source using this commit https://github.com/neovim/neovim/commit/6a580b997b9f8124d23ca6c87a47b4fec2e3e9e7

No, I'm suggesting that the fix is hard, and should not be rushed, since otherwise it would already have been done a long time ago. And reverting is probably a...

NOTE: I was going to report `xsel` as a workaround, but that one does not close `stdout` and `stderr` either. So a similar workaround is needed for that as well,...

I integrated this into Neovide here https://github.com/neovide/neovide/pull/1985 However, there's one problem. When I run `:intro` manually, it first shows the text `press ENTER or type command to continue`, before showing...

I agree, it's pretty hard to do correctly, and needs to be coupled by something like this https://github.com/neovide/neovide/blob/a27de281d4d2eea22228b41712ae58dab6c95898/lua/intro.lua. It does the following things: 1. Center the lines 2. Center the...