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.
On Sat, Jun 17, 2023, 9:59 AM Bram Moolenaar wrote:
>
> Robert Solomon wrote:
>
> [...]
>
> > I learned there that vim is known to disli
, or TakeCommand.
I was having trouble in ALL of the windows terminal programs. The same
solution worked for all of them.
--rob solomon
On Monday, June 5, 2023 at 2:22:14 AM UTC-4 Christian Brabandt wrote:
>
> On Sa, 03 Jun 2023, Robert Solomon wrote:
>
> > My point is differ
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
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.
This makes terminal mode Vim unusable for me. I've seen this in
Is there anything I can do about this?
Is this expected behavior?
On Sunday, September 25, 2022 at 10:56:05 AM UTC-4 Robert Solomon wrote:
> No.
> The context is that sometimes when I do
>
> Git commit
>
> I get that screen. I use vim as my git editor
>
>
> On
No.
The context is that sometimes when I do
Git commit
I get that screen. I use vim as my git editor
On Sun, Sep 25, 2022, 2:24 AM Steve Martin wrote:
> Actually That looks like the kind of thing that happens when you paste
> some new text into VIM without switching to Paste mode
I forgot to add that this is on a Windows 10 computer running gvim 8.2 w/
patches including 3049.
On Sunday, July 18, 2021 at 9:18:36 AM UTC-4 Robert Solomon wrote:
> I often copy-paste from a browser into a text file to save the content I
> come across. When I try to save the file, I
I often copy-paste from a browser into a text file to save the content I
come across. When I try to save the file, I often get a conversion error.
I have to manually go thru each error and change the extended character to
an ascii one.
I don't understand why this happens. Any file I see is
I am unclear how to install 64 bit vim on windows 10. The nightly builds
on the vim win32 installer have an installer gvim_8.1._x86.exe that is
the primary one. But there is also _x64.zip, and I don't know how to use
it.
There is now a _x64.exe installer labeled experimental.
How do the
I cloned the github source and compiled vim 8.1. That went smoothly.
How do I get gvim 8.1 on Ubuntu?
Thx
Rob
--
--
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
win 10 amd64
I d/l and installed gvim81.exe.
Neither vim nor gvim recognize F11 or F12. This was not true in version 8.0.
Is this a known issue?
--rob
--
--
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
13 matches
Mail list logo
