Thank you for the operation report.
The flickering is because the VTP format is output to Take command v25
where VTP does not exist.
I am currently writing a patch that teaches Vim support for VTP. It seems
to solve it.
--
Nobuhiro Takasaki
--
--
You received this message from the "vim_use"
version 8.1.2424.x64 now works on take command 25. I see a flickering
screen for about 1 second before it stabilizes.
I guess a terminal is failing, but that is now handled effectively on my
computer.
--rob solomon
On 12/9/19 6:44 PM, rob wrote:
I am a little confused, also. I looked
Christian wrote:
> > On Mo, 09 Dez 2019, Bram Moolenaar wrote:
> >
> > > Is that possible for the gvim.exe that I create? Or do we need to pick
> > > the right one from your site? I'm sure many users would prefer a signed
> > > binary. Not sure if it runs everywhere, e.g. on Windows XP?
On Di, 10 Dez 2019, Christian Brabandt wrote:
>
> On Mo, 09 Dez 2019, Bram Moolenaar wrote:
>
> > Is that possible for the gvim.exe that I create? Or do we need to pick
> > the right one from your site? I'm sure many users would prefer a signed
> > binary. Not sure if it runs everywhere,
On Mo, 09 Dez 2019, Bram Moolenaar wrote:
> Is that possible for the gvim.exe that I create? Or do we need to pick
> the right one from your site? I'm sure many users would prefer a signed
> binary. Not sure if it runs everywhere, e.g. on Windows XP? That's why
> I have been using MSVC
It was a conclusion after misreading the code. Everything is my mistake.
I was confused because the timing and content of the event arrived
completely different from cmd.exe.
There are two causes:
I was ignoring failures that occurred when changing the window size. (There
is a terminal that
I am a little confused, also. I looked at the limited forum discussion.
You wrote
The values are different:
INPUT_RECORD.Event.WindowBufferSIzeEvent.dwSize
You are: return the size of the window buffer. (Screen Buffer Size)
Correctly: return the size of the displayed window in characters.
Christian wrote:
> On Sa, 07 Dez 2019, Bram Moolenaar wrote:
>
> > As a tryout for the upcoming Vim 8.2 release I created an MS-Windows
> > self-installing binary from the current Vim version. This should be
> > very close to the Vim 8.2 release. Give it a try.
> >
> > This uses the new
On Sa, 07 Dez 2019, Bram Moolenaar wrote:
> As a tryout for the upcoming Vim 8.2 release I created an MS-Windows
> self-installing binary from the current Vim version. This should be
> very close to the Vim 8.2 release. Give it a try.
>
> This uses the new Windows installer, which is nicer
I have confirmed.
Patch 8.1.0940: MS-Windows console resizing not handled properly
This was the cause.
The value returned by Take Command seems toe be different.
INPUT_RECORD.Event.WindowBufferSIzeEvent.dwSize
Correctly returns the number of characters in the window.
Now the window buffer size
I read it now. I'm going to fix it.
There is a patch that I wrote a long time ago, it seems that it will fix
the destruction of the screen.
I don't know about F11 and F12 right now. I will investigate.
--
Nobuhiro Takasaki
--
--
You received this message from the "vim_use" maillist.
Do not
Rob Solumon wrote:
> I've been using gvim for windows 10 installed from gvim_8.1.0451_x86.exe
> since that came out. That was the first version that fixed the bug in
> vim (non-gui mode) in which and were not recognized.
>
> That has worked fine for me.
>
> At Bram's request, I installed
I've been using gvim for windows 10 installed from gvim_8.1.0451_x86.exe
since that came out. That was the first version that fixed the bug in
vim (non-gui mode) in which and were not recognized.
That has worked fine for me.
At Bram's request, I installed gvim_8.1.2410_x64.exe and
As a tryout for the upcoming Vim 8.2 release I created an MS-Windows
self-installing binary from the current Vim version. This should be
very close to the Vim 8.2 release. Give it a try.
This uses the new Windows installer, which is nicer than the old one.
It also has translations for a few
14 matches
Mail list logo
