Saturday, June 17, 2023

Re: BUG: terminal vim 9.0.1506 x64 window 10

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 <Bram@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 -- Bram@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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJTu_taLhuz-BabMoBoaR9dLNx5OW-ej4j0WiP4hUGVAVhjinQ%40mail.gmail.com.

No comments: