fredizzimo

Maybe it would make more sense to extract this as a standalone vim plugin? It would be easier to install, and the black maintainers don't need to deal with any...

I think that this might have fixed the original issue * https://github.com/neovide/neovide/pull/2354 The problem @shivamchandra75 has is different, and I think it's caused by some plugins and not by Neovide,...

If that's not the case, could you attach a tracy log following the instructions here https://neovide.dev/troubleshooting.html#performance-profiling?

@rp1231, are you able to build main from source? There was a bug with loading Cascadia Code that was fixed here: * https://github.com/neovide/neovide/pull/2354 If that does not help I guess...

@rp1231 I might look at this a bit more later, but my first impression is that it does not have anything to do with the fonts in this case, but...

@rp1231, well, in the profiler I saw one frame that was over 100 ms, because the vsync detection did not trigger, and another frame that took too long to render...

@rp1231, yes, that's also a valid method. I'm not sure why the command did not work though, but maybe there's some difference in the windows version.

Thanks. There has to be something going on, on the GPU side, every animation looks roughly like this  Where the only information we have, is that it's waiting for...

It looks as if something might be too heavy on the GPU side, which is strange, since your graphics card should definitely be good enough. Only the first frames are...

The trace looks very strange. I guess I have to compare how it looks on my system to know what's going on. But it might just be that the gpu...