Tuesday, May 30, 2023

Re: Multiple windows get corrupted

Everybody FYI... I thank all the replies I have gotten related to this issue which I should mention I have not figured out what the cause is. I followed the suggestion provided and was not able to find which, if any, plugin caused it. However, by pure chance I recently discovered one thing. So when that text garbling happened (and happened very often), I just used exit my vim session and open all files in session until next time it misbehaved again. Well the discovery that I made recently is that when that happened to me, instead of exiting, I could either pull the right edge of the window either in or out for a pixel or two OR snap the vim session window to either left or right (on linux like using super key and left/right arrow keys) of the screen and it refreshed my windows/buffers and things would look normal until next time it misbehaved.
Does this discovery point in any direction as to what my issue is and how to remedy it permanently?

Thanks in advance.
Ben

On Saturday, December 31, 2022 at 5:38:50 AM UTC-6 Enan Ajmain wrote:
On Fri, 30 Dec 2022 21:17:26 -0800 (PST)
Ben Mehmet <ozu...@gmail.com> wrote:
> Could you help with recommending how to proceed with my .vimrc and
> plugins to find the culprit? I mean how should I start incorporating
> my settings in?

https://vi.stackexchange.com/questions/2003/how-do-i-debug-my-vimrc-file

--
Enan
3nan....@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/9093484c-7a71-403b-8853-f4213c33e8b9n%40googlegroups.com.

No comments:

Post a Comment