fredizzimo

The easiest way to debug Neovide is probably with Visual Studio code, settup up DAP in neovide is a bit trickier, and I don't even have it setup myself, so...

A log file was provided in: * #2462 > TRACE [neovide::renderer::vsync::vsync_macos] Window moved to a new screen, try to re-create the display link. > TRACE [neovide::renderer::vsync::vsync_macos] Succeeded to create display...

@ngseba, let's continue here It looks like the communication with Neovim dies. This is the last indication of any communication happening > TRACE [neovide::bridge::ui_commands] Keyboard Input Sent: Can you test...

In that case, there are two possible fixes, both requires Neovim nightly. The first one is this: * https://github.com/neovim/neovim/pull/27348 The second one is this Neovide PR with a very recent...

@pidgeon777, I'm not sure why it's failing, it should direct3d itself should only enable those when debugging. But if you can build from source, you could try deleting these lines:...

The fix is actually in Neovim, not Neovide, and according to @ngseba, 0.12.2 should work as well. So, you will have to update to Neovim nightly.

Yes, the random freeze. The startup crash can probably be fixed by deleting the lines I pasted above or using Neovide 12.2 instead of the git build.

The issue should be fixed in the latest nightly build of Neovim, the 0.9.5 version does not include my fix that I linked earlier: * https://github.com/neovim/neovim/pull/27348 But there was also...

Can you all test with the latest Neovim nightly build from today? There's another potential fix here * https://github.com/neovim/neovim/pull/28717

I haven't verified it, but this is most certainly caused by this hack: https://github.com/neovide/neovide/blob/71e9fa49fcb393662ee03e42968724b91cde8e62/src/editor/mod.rs#L482-L503, Originally introduced here, but further improved later: * https://github.com/neovide/neovide/pull/753 The hack is unfortunately needed, since Neovim...