fredizzimo

Yes, we have another issue open for the remote clipboard * https://github.com/neovide/neovide/issues/2613 In your case, I think you can get it to work by setting `vim.g.clipboard=false`, which should disable the...

The async will block on that line, so the logs should be valid. That means that there are only two otjer possible places for it to hang, 1. The echo...

It will probably hang later, but it's worth trying to comment out the echo and version check.

I'm sorry but, I don't think I can help you anymore without being able to reproduce the problem myself. I think this is related to the general windows pipe communication...

@chevcast, can you attach the logs from `neovide --log`? And I guess you are using Neovide 0.15.0, right?

Are you able to verify that nvim is actually running inside WSL? Maybe there's something in you shell startup scripts that's blocking and prevents it from even starting?

I can replicate the same results with https://game.intel.com/us/intel-presentmon/, which is far more reliable. However, I don't think there's much that can be done about it, the lag consist of the...

@xzbdmw, no not unless you have some plugin on the Neovim side that slows things down. Or maybe if there's something wrong with the blur/shadow/transparency rendering, but that can only...

@xzbdmw, the long "frame" you see there is in fact several frames if you zoom in. The reason why it appears to do that is that there's no animation in...

You can easily find examples of it taking longer, for example here, from the `no-multigrid-clean` log. https://github.com/neovide/neovide/issues/2602#issuecomment-2156022241 There's one thing I don't understand though, you say that you run with...