Ok. Thanks for all the help. I hope to report back in a couple of weeks. On Friday, June 2, 2023 at 9:14:09 AM UTC-4 Bram Moolenaar wrote:
> > > > > > > As I mentioned in my post that begins with "Everybody FYI" I had > just > > > > > > recently discovered that pulling the edge of the window left > > > > > > or right when the garbling happened it *made *it the problem > > > > > > go away. But I was hoping to find a fix for my problem so > > > > > > that it doesn't happen; specially when I am pair coding with a > > > > > > colleague. It gets frustrating specially since I couldn't > > > > > > figure out yet a keyboard short cut for pulling side of window > > > > > > left or right. > > > > > > > > > > OK, so just before resizing the window manually Vim somehow is in > a bad > > > > > state. It most likely is related to how the Vim window was > resized. Do > > > > > you know? In case you are not sure you could use: > > > > > > > > Yes. As I mentioned before I would resize the window to accommodate > for a > > > > opening another file in side window. > > > > > > The big question is: HOW did you resize the window? Resizing manually > > > fixes the problem, thus you didn't resize it the normal way, right? > > > > Oh. Missed your question here. So I would just use the mouse to pull the > > side of the window out to make the window wider. > > But then you can avoid the problem by doing it again? That doesn't give > any hint about why it happened the first time. Can you think of > anything that might matter? > > > > > > verbose set columns? > > > > > verbose set lines? > > > > > > > > > > Hopefully this leads to some Vim script or an autocommand that > triggers > > > > > the problem. We need this to be able to write a test for it > anyway. > > > > > Note that you need to start Vim with "--clean" to make sure your > local > > > > > setup doesn't change what happens. > > > > > > > > Regarding starting Vim with "--clean". The "--clean" option was > suggested > > > > sometime at the start of this thread. It ran with no issues but it > also > > > > considerably limited my editing capabilities. > > > > > > The idea is that you start Vim with "--clean" and then add pieces of > > > your setup until you find out what piece matters for reproducing the > > > problem. Hopefully not including a whole plugin, since then we would > > > need to dig into that plugin. > > > > > > " Hopefully not including a whole plugin, since then we would need to > dig > > > into that plugin." ??? > > > > Not clear on this. > > What does "add pieces" mean? Does it mean pieces of the the vimrc file > or > > adding plugins one by one or is it actually both? > > Both. In the case of using your vimrc file, you can put a "finish" > command in various places and see what the effect is. Binary search > should work fastest. But start by putting it near the top to check that > it actually matters to be there at all. > > For plugins you could rename them temporarily, e.g. by changing ".vim" > to ".skip". > > -- > From "know your smileys": > :-* A big kiss! > > /// 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/a7949dd1-c5ef-4d1b-a63b-a4b35b299133n%40googlegroups.com.
