> 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.
OK, so this is for when Vim is started
On Wed, 21 Jun 2023 19:16:28 +0200
Christian Brabandt wrote:
> > Am 21.06.2023 um 18:13 schrieb Enan Ajmain <3nan.ajm...@gmail.com>:
> >
> > ___On Wed, 21 Jun 2023 13:41:03 +0100
> > Bram Moolenaar wrote:
> >> Can we assume that MS Terminal is included with the distribution, or
> >> installed
It's true.
I use TCCLE (free version of Take Command) as a command-line shell on my
Windows machine. In an April round of updates, Windows 11 shifted to
opening TCCLE as a tab in a MS Terminal window rather than independently
as in the past. Fortunately, with a published hack I change Windows 11
> Am 21.06.2023 um 18:13 schrieb Enan Ajmain <3nan.ajm...@gmail.com>:
>
> On Wed, 21 Jun 2023 13:41:03 +0100
> Bram Moolenaar wrote:
>> Can we assume that MS Terminal is included with the distribution, or
>> installed most widely? If so, then investing time in making this work
>> properly
On Wed, 21 Jun 2023 13:41:03 +0100
Bram Moolenaar wrote:
> Can we assume that MS Terminal is included with the distribution, or
> installed most widely? If so, then investing time in making this work
> properly is well worth it.
Windows 11 comes with MS Terminal and is the default [1]. As for
> On Tue, 20 Jun 2023 22:52:05 -0700 (PDT)
> Steve Martin wrote:
> > [...]
> >
> > Using the Windows CMD shell under the old CMD terminal, whatever that
> > is called
>
> It's Console Host or Conhost in short.
There also is mention of "Win32 virtual console", the +vtp feature.
This is
> 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.
If
On Wed, 21 Jun 2023 04:05:52 -0700 (PDT)
"rwmit...@gmail.com" wrote:
> Wow, that must have really hit a nerve for you to go into such
> lengths for a platform that is and has always been subpar, always
> several years behind everyone else.
Couldn't agree more. On Windows being subpar. Not on
Wow, that must have really hit a nerve for you to go into such lengths for
a platform that is and has always been subpar, always several years behind
everyone else.
On Wednesday, June 21, 2023 at 2:27:59 AM UTC-4 Enan Ajmain wrote:
> On Tue, 20 Jun 2023 22:52:05 -0700 (PDT)
> Steve Martin
On Tue, 20 Jun 2023 22:52:05 -0700 (PDT)
Steve Martin wrote:
> [...]
>
> Using the Windows CMD shell under the old CMD terminal, whatever that
> is called
It's Console Host or Conhost in short.
> Personally I use bash and Windows Terminal when I'm on Windows. It
> has features I prefer and I
To be clear, testing on various terminals on Windows results in the
following conclusions.
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.
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
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
> >
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.
>
> After setting the window size, I start vim using my _vimrc as I
On Fri, Jun 16, 2023 at 6:28 PM 'Susan McElheny' via vim_use <
vim_use@googlegroups.com> wrote:
> I have used VI on Unix for over 30 years and now have to use it in Windows
> where it works much differently. If I open gVim 9.0 in a GUI session, how
> do I open another file without having to go
On Fri, 16 Jun 2023 12:27:59 -0400
"'Susan McElheny' via vim_use" wrote:
> I have used VI on Unix for over 30 years and now have to use it in Windows
> where it works much differently. If I open gVim 9.0 in a GUI session, how
> do I open another file without having to go to the top with my mouse
> - 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
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.
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
> 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
Quick experimentation indicates that console mode vim fails when width >=
250. But not every time.
I don't think height matters.
On Sat, Jun 17, 2023, 9:59 AM Bram Moolenaar wrote:
>
> Robert Solomon wrote:
>
> [...]
>
> > I learned there that vim is known to dislike non-standard terminal
>
I use :tabedit FILE
On Friday, June 16, 2023 at 12:36:09 PM UTC-4 jr wrote:
> hi,
>
> On Fri, 16 Jun 2023 at 17:28, 'Susan McElheny' via vim_use
> wrote:
> >
> > I have used VI on Unix for over 30 years ... how do I open another file
> without having to go to the top with my mouse and select
hi,
On Fri, 16 Jun 2023 at 17:28, 'Susan McElheny' via vim_use
wrote:
>
> I have used VI on Unix for over 30 years ... how do I open another file
> without having to go to the top with my mouse and select File, Open? At the
> command level I can just :vi "filename", ...
I've used Vim on
I have used VI on Unix for over 30 years and now have to use it in Windows
where it works much differently. If I open gVim 9.0 in a GUI session, how
do I open another file without having to go to the top with my mouse and
select File, Open? At the command level I can just :vi "filename", but
hi,
On Fri, 16 Jun 2023 at 15:54, Robert Solomon wrote:
> ...
> I learned there that vim is known to dislike non-standard terminal sizes.
?? why do you write this[*], when followed by:
> So I made the terminal windows smaller and it started to work.
> ...
> I was having trouble in ALL of the
I've been away.
I was having trouble w/ the console version of vim 9 in windows terminal
and cmd.exe as well as take command.
I also posted on the forum for JPSoft's take command.
I got a response there that was helpful. Interesting, none of the
responses here were helpful.
I learned there
On Sa, 03 Jun 2023, Robert Solomon wrote:
> My point is different. It's isn't working correctly on ANY of them.
That is hardly correct. I haven't heard from many complaints about using
Vim terminal in neither Windows nor Linux.
> see
> Of course vim can't possibly support all possible terminals
>
> My point is different. It's isn't working correctly on ANY of them.
>
> see https://github.com/microsoft/terminal/issues?q=vim+in%3Atitle+
That search results in several issues, which one is this about?
This is about one
And
https://jpsoft.com/forums/threads/incompatibility-of-tcmd-30-and-vim9.11517/unread?new=1
--
rob
r...@drrob1.com
On Sat, Jun 3, 2023, at 9:20 PM, Robert Solomon wrote:
> Of course vim can't possibly support all possible terminals
>
> My point is different. It's isn't working
Of course vim can't possibly support all possible terminals
My point is different. It's isn't working correctly on ANY of them.
see https://github.com/microsoft/terminal/issues?q=vim+in%3Atitle+
On Saturday, June 3, 2023 at 4:04:44 PM UTC-4 aro...@vex.net wrote:
>
> > Vim can't possibly add
> Vim can't possibly add code to support each peculiarity of each of them.
> I'm not sure what generic problem exists that is not terminal-specific.
>
The early days of Unix coincided with a Cabrian explosion of physical
terminals. This led to the development of a database of terminal
attributes
> Which program do you mean when you say the good-old windows console
> and the newer windows terminal?
The Windows console is what was originally the console in MS-Windows.
Perhaps people refer to it as command.com or cmd.exe.
AFAIK this is available on every MS-Windows installation without
Which program do you mean when you say the good-old windows console and the
newer windows terminal?
Others are reporting that vim does not work correctly in the current
windows terminal. I just read in the JPSoft forum that the screen is
scrambled upon exiting vim when called from windows
> I use JPSoft's take command as by command interpreter. Now at version 29.
> When I start vim in the terminal, it does not update the screen correctly.
> Contents from longer lines remain on screen when the file has shorter lines.
I don't know the "take command". Is this a kind of shell?
I use JPSoft's take command as by command interpreter. Now at version 29.
When I start vim in the terminal, it does not update the screen correctly.
Contents from longer lines remain on screen when the file has shorter lines.
This makes terminal mode Vim unusable for me. I've seen this in
35 matches
Mail list logo
