akiyosi

> Okay, thanks. Will this be in consideration for the future? (should I keep this issue open for now) ok, I will consider. I think it is best for neovim...

Related to https://github.com/neovim/neovim/pull/12355

@valignatev hi, Thanks for this report. Just to confirm, do the following settings change the behavior of this issue? ``` # Put the following in setting Cacheddrawing = false ```...

@valignatev Thanks for the confirmation! I've created a trial fix for this issue. Could you please check the reproducibility of the issue with the binary generated by CI as follows?...

@valignatev Thanks for confirming. Hmm, I see that this problem does not occur with Neovim-qt, and I referred to the following code for Neovim-qt, but I may still be missing...

@valignatev Thank you. By the way, in the above test artifact, does the behavior change depending on whether the following goneovim config setting is enabled or disabled? ``` # Put...

@valignatev Hmmm, I have tried to reproduce this problem on 96 and 144 DPI monitors respectively, but could not reproduce it successfully. Maybe there is some additional factor...? I will...

I thought I understood that, and in fact I was trying to reproduce the problem by dragging the goneovim editor started in one to the other. However, the display did...

By the way, Neovim-qt has reported a similar problem before. Am I correct in understanding that it looks similar to the screenshot as posted in this problem report? https://github.com/equalsraf/neovim-qt/issues/391

Thanks for the screenshots! It's very helpful. Is there any change in the behavior of the following CI artifacts? https://github.com/akiyosi/goneovim/actions/runs/1809691548