fredizzimo
fredizzimo
I have noticed this myself, and I think I know the cause, but have not completely verified it. It seems like there's a bug here, which forces it to catch...
This was fixed in https://github.com/neovide/neovide/pull/2472
Those elements are actually drawn with foreground colors, and we can't apply transparency to that, or the text would be transparent as well. So, we need more support from Neovim...
Meanwhile, we could perhaps add a setting that only applies transparency to the default neovim background color. ~But that will come with other drawbacks like this~ * ~https://github.com/neovide/neovide/issues/1508~ Edit: that...
I created a proposal for dealing with global transparency * #2471
I'm re-opening, since #2478 was reverted.
I'm re-opening this, but we need to open an upstream Neovim bug report for that. I will do that a bit later, since the proper bug reports that needs a...
We will need profiling data to track this down further. I will give furhter instructions next week.
The instructions are now in a more readable format here https://neovide.dev/troubleshooting.html#performance-profiling
This will be very hard to track down, I'm personally using the built in terminal constantly, but not through toggleterm, I use vim-floaterm. But I have never seen any freezes...