> - start "vim --clean" > - :set columns=260 > - :term > - vim --clean somefile > - ?
Wait, are we saying that we're setting the internal vim 'columns' to something other than the terminal's size? Because if that is the case, I can clearly see an issue is going to be caused when the Terminal does not resize when asked by vim. This definitely does cause problems in Windows Terminal. The window is corrupted and even exiting vim the window has issues as it is still the same size, but the shell reports ColumnsxLines=NEWColumnsxLines and nothing works well after that. --- Should my CPU be smoking? On Saturday, June 17, 2023 at 7:09:39 PM UTC-6 Steve Martin wrote: > I'm puzzled by this, and have to believe this must be either a terminal > problem or some vim plugin interaction with that terminal. > > I just used Windows Terminal (Preview to be exact) set to max screen size > (2560x1440) and set the font to 6pt. > > That results in terminal Lines x Columns=134x585. Five hundred and eighty > five characters across. My old eyes had problems seeing that. Still, > nothing untoward happened in VIM. I edited some large files and tried > various "command type" things. No problems. > > I'm really curious what problems people are having and what is causing it > for some and not for others. > > BTW: vim v9.0.1637, as I tend to build vim nightly for my regular use. > Windows 11. > > On Saturday, June 17, 2023 at 2:30:54 PM UTC-6 Robert Solomon wrote: > >> To be clearer: >> >> Windows 10 >> >> My quick testing involved me starting take command and using the mouse to >> size the window. Take command shows the window size in the bottom right >> corner. >> >> After setting the window size, I start vim using my _vimrc as I usually >> do. I did not change anything from within vim. >> >> >> >> On Sat, Jun 17, 2023, 4:06 PM Bram Moolenaar <br...@moolenaar.net> wrote: >> >>> >>> > Quick experimentation indicates that console mode vim fails when width >>> >= >>> > 250. But not every time. >>> > >>> > I don't think height matters. >>> >>> OK, so what reproduction steps are required? I tried this: >>> >>> - start "vim --clean" >>> - :set columns=260 >>> - :term >>> - vim --clean somefile >>> - ? >>> >>> I could not make this show any problems. This might be because I'm >>> using Linux. Or: >>> >>> - What would be the content of "somefile"? I tried some long (wrapping) >>> lines and a few short lines. >>> - What commands do you use once "somefile" is loaded? Move the cursor, >>> join/split lines, etc.? >>> >>> I hope you can give an example that is simple and reproduces the problem >>> consistently. >>> >>> -- >>> I thought I was eating a crab salad. It turned out to be a crap salad. >>> >>> /// 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/b18efb30-b75f-4f25-8e4a-cf3ece5d4e53n%40googlegroups.com.
