[vim/vim] Make conpty default on Windows 11 (PR #19037)

13 views
Skip to first unread message

BenYip

unread,
Dec 28, 2025, 4:28:52 PM (21 hours ago) Dec 28
to vim/vim, Subscribed

Conpty was first introduced in 2018, and it's stable on Windows 11 now.

fix #19033


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/19037

Commit Summary

  • f0468c0 Make conpty default on Windows 11

File Changes

(1 file)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19037@github.com>

BenYip

unread,
Dec 28, 2025, 4:48:21 PM (21 hours ago) Dec 28
to vim/vim, Subscribed
bennyyip left a comment (vim/vim#19037)

We only have special logic for conpty_type = 2 and conpty_fix_type<1, which works around windows bug.
On Windows 11, conpty_type=0 and conpty_fix_type=1. It should be OK with these values.

Related commit and PR:
57da698
#4411


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19037/c3695073022@github.com>

Christ van Willegen

unread,
3:09 AM (11 hours ago) 3:09 AM
to vim...@googlegroups.com, reply+ACY5DGDQXDNROFJMVN...@reply.github.com, vim/vim, Subscribed
While you're here: 

  // Notes:
- // Win 10 22H2 Final is build 19045, it's conpty is widely used.
+ // Win 10 22H2 Final is build 19045, its conpty is widely used.
  // Strangely, 19045 is newer but is a lower build number than the 2020 insider

Op zo 28 dec 2025, 22:48 schreef BenYip <vim-dev...@256bit.org>:
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_dev/vim/vim/pull/19037/c3695073022%40github.com.

vim-dev ML

unread,
3:09 AM (11 hours ago) 3:09 AM
to vim/vim, vim-dev ML, Your activity
vim-ml left a comment (vim/vim#19037)
While you're here:

// Notes:

- // Win 10 22H2 Final is build 19045, it's conpty is widely used.

+ // Win 10 22H2 Final is build 19045, its conpty is widely used.

// Strangely, 19045 is newer but is a lower build number than the 2020
insider

Op zo 28 dec 2025, 22:48 schreef BenYip ***@***.***>:

> *bennyyip* left a comment (vim/vim#19037)
> <https://github.com/vim/vim/pull/19037#issuecomment-3695073022>
>
> We only have special logic for conpty_type = 2 and conpty_fix_type<1,
> which works around windows bug.
> On Windows 11, conpty_type=0 and conpty_fix_type=1. It should be OK with
> these values.
>
> Related commit and PR:
> 57da698
> <https://github.com/vim/vim/commit/57da69816872d53038e8a7e8dd4dc39a31192f0d>
> #4411 <https://github.com/vim/vim/pull/4411>
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/vim/vim/pull/19037#issuecomment-3695073022>.
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
> --
> --
> You received this message from the "vim_dev" 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_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ***@***.***
> <https://groups.google.com/d/msgid/vim_dev/vim/vim/pull/19037/c3695073022%40github.com?utm_medium=email&utm_source=footer>
> .
>


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19037/c3695791666@github.com>

BenYip

unread,
6:07 AM (8 hours ago) 6:07 AM
to vim/vim, vim-dev ML, Comment
bennyyip left a comment (vim/vim#19037)
What do you mean? I don't understand.


On 2025-12-29, vim-dev ML wrote:
>vim-ml left a comment (vim/vim#19037)
>
>While you're here:
>
> // Notes:
>
>- // Win 10 22H2 Final is build 19045, it's conpty is widely used.
>
>+ // Win 10 22H2 Final is build 19045, its conpty is widely used.
>
> // Strangely, 19045 is newer but is a lower build number than the 2020
>insider
>
>Op zo 28 dec 2025, 22:48 schreef BenYip ***@***.***>:
>
>> *bennyyip* left a comment (vim/vim#19037)
>> <https://github.com/vim/vim/pull/19037#issuecomment-3695073022>
>>
>> We only have special logic for conpty_type = 2 and conpty_fix_type<1,
>> which works around windows bug.
>> On Windows 11, conpty_type=0 and conpty_fix_type=1. It should be OK with
>> these values.
>>
>> Related commit and PR:
>> 57da698
>> <https://github.com/vim/vim/commit/57da69816872d53038e8a7e8dd4dc39a31192f0d>
>> #4411 <https://github.com/vim/vim/pull/4411>
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <https://github.com/vim/vim/pull/19037#issuecomment-3695073022>.

>> You are receiving this because you are subscribed to this thread.Message
>> ID: ***@***.***>
>>
>> --
>> --
>> You received this message from the "vim_dev" 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_dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ***@***.***
>> To view this discussion visit
>> https://groups.google.com/d/msgid/vim_dev/vim/vim/pull/19037/c3695073022%40github.com
>> <https://groups.google.com/d/msgid/vim_dev/vim/vim/pull/19037/c3695073022%40github.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
>--
>Reply to this email directly or view it on GitHub:
>https://github.com/vim/vim/pull/19037#issuecomment-3695791666
>You are receiving this because you authored the thread.
>
>Message ID: ***@***.***>


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: <vim/vim/pull/19037/c3696193922@github.com>

Christ van Willegen

unread,
6:24 AM (7 hours ago) 6:24 AM
to vim...@googlegroups.com, reply+ACY5DGDE4HPJC6MTC6...@reply.github.com
Hi,

Op ma 29 dec 2025, 12:07 schreef BenYip <vim-dev...@256bit.org>:
bennyyip left a comment (vim/vim#19037)
What do you mean? I don't understand.

There is a spelling error in that comment...

Christ van Willegen

vim-dev ML

unread,
6:24 AM (7 hours ago) 6:24 AM
to vim/vim, vim-dev ML, Your activity
vim-ml left a comment (vim/vim#19037)
Hi,

Op ma 29 dec 2025, 12:07 schreef BenYip ***@***.***>:


> *bennyyip* left a comment (vim/vim#19037)
> <https://github.com/vim/vim/pull/19037#issuecomment-3696193922>

> What do you mean? I don't understand.


There is a spelling error in that comment...

Christ van Willegen


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19037/c3696254956@github.com>

BenYip

unread,
12:12 PM (2 hours ago) 12:12 PM
to vim/vim, vim-dev ML, Push

@bennyyip pushed 1 commit.


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19037/before/f0468c0a7083e40abd52d3a26243e4c8201cbd52/after/93a1366bd772eb82cf3f0b65234a3600aeeba22c@github.com>

Reply all
Reply to author
Forward
0 new messages