Ok. So as expected it happened again. And I followed the steps you (Bram) mentioned. I have following diffs between the bad (left side) and good (right side):
columns=258 <-----> columns=120 lines=72 <-----> lines=60 modified <-----> nomodified scroll=35 <-----> scroll=29 window=71 <-----> window=59 lines, columns, and window are set in my .gvimrc. I am experimenting with commenting them out to see if any effect. Any ideas from your side? Thanks. On Wednesday, May 31, 2023 at 10:11:40 AM UTC-4 Ben Mehmet wrote: > Thank you. I will follow the troubleshooting steps you highlighted. > > On Wednesday, May 31, 2023 at 7:48:24 AM UTC-4 Bram Moolenaar wrote: > >> >> > 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? >> >> Perhaps a window resize event makes Vim recompute some things and then >> it works again? Just guessing. >> >> If some option gets a wrong value, such as 'lines' or 'columns', that >> would cause display errors. You could do the following: >> >> redir > /tmp/settings_1 >> set! all >> redir END >> >> Do this when everything works OK and later when things are wrong, using >> a different file name. Then compare the output and try to spot the >> difference. If you see an option with a suspect value, you can possibly >> find out where it was set with e.g.: >> >> :verbose set lines? >> >> -- >> From "know your smileys": >> 8<}} Glasses, big nose, beard >> >> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net >> \\\ >> /// \\\ >> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// >> \\\ help me help AIDS victims -- http://ICCF-Holland.org /// >> > -- -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/92d48f21-370c-4e61-a589-d01540070420n%40googlegroups.com.
