On Windows Terminal Preview (Windows 11) with Windows PowerShell or CMD as the shell, the 'columns=600' or any other such setting will be ignored and the variable will remain at whatever vim set it to. So nothing happens to the display.
Using the Windows CMD shell under the old CMD terminal, whatever that is called, will result in columns value being changed, but the terminal does not change and has no issues after the setting.
Using RedHat's cygwin bash, which comes with Git-Desktop for instance, inside of Windows Terminal, performing a "set columns=600" will result in a corrupted terminal which cannot be fixed using the standard terminal reset commands (tset(1) or reset(1)). Only closing and reopening the terminal will return a good work session.
Using cygwin bash under the RedHat provided mintty terminal and performing a "set columns=600" will cause vim to resize to the maximum width of the system monitor and set Columns to a number that equates to the new terminal size. This is the only terminal software I found that behaves as one would expect a Linux terminal to work. This was the best terminal I saw on Windows.
Finally, using the GVim provided with VIM for Windows will also change the Terminal size according to changes in the 'columns' setting. Again, vim will change the size of the terminal up to the actual maximum available on the system monitor. The columns variable reflects the proper terminal size like the mintty version does. I don't know what terminal that means is used or even if it can be called a terminal, but clearly it works properly with vim by design.
So my conclusion is that this is a terminal software problem. Some terminals adhere to the resizing commands that vim sends, some ignore it but remain stable, and yet others become hopelessly corrupted requiring that the software be closed and restarted.
Obviously Bram knows far more than I do, but my recommendation would be to use a Terminal package that behaves like a fully functional soft terminal should or don't resize the window after launching VIM.
Personally I use bash and Windows Terminal when I'm on Windows. It has features I prefer and I don't usually resize my work space after I've got set up. Will Microsoft fix their issues. Not gonna hold my breath.
In the end there are a lot of choices out there, which can be both good and bad.
__
Should there be smoke coming out of my CPU?
On Tuesday, June 20, 2023 at 1:47:23 AM UTC-6 Steve Martin wrote:
Looking at the Take Command website and Googling about it I can find no reference to Take Command as a Terminal emulator anywhere. I am guessing it has very basic, if any, capabilities at all. Thus it probably doesn't heed any ':set columns=' or other vim terminal commands.On Monday, June 19, 2023 at 12:32:07 PM UTC-6 Ed Blackman wrote:On Mon, Jun 19, 2023 at 09:53:12AM +0200, Christian Brabandt wrote:
> On Sa, 17 Jun 2023, Robert Solomon wrote:
> > 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.
>
> So, can you reproduce the issue using `vim --clean` to disable any of
> your usual customizations? What exactly is this `take` command. Does it
> reproduce without it?
>
> What terminal did you use, you said?
Take Command is a replacement shell (and maybe a replacement terminal?) for Windows: https://jpsoft.com/products/take-command.html
I don't know anything about it, but thought I'd interject to clarify.
--
Ed Blackman
--
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/bea3e0f6-94f4-421c-a9e0-c85e056a4987n%40googlegroups.com.
No comments:
Post a Comment