[vim/vim] docs: better way to detect WSL (PR #20714)

Mao-Yining

unread,

Jul 5, 2026, 8:46:50 AM (18 hours ago) Jul 5

to vim/vim, Subscribed

Current method can't work in Windows Terminal as far as I know.

This is a way that already had been adopted in dist/vim9.vim.

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

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

Commit Summary

0c3b9cf docs: better way to detect WSL

File Changes

(1 file)

M runtime/doc/os_win32.txt (2)

Patch Links:

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.

Maxim Kim

unread,

Jul 5, 2026, 8:53:57 AM (18 hours ago) Jul 5

to vim/vim, Subscribed

habamax left a comment (vim/vim#20714)

Current method can't work in Windows Terminal as far as I know.

This is a way that already had been adopted in dist/vim9.vim.

It works there just fine.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.

Mao-Yining

unread,

Jul 5, 2026, 8:57:30 AM (18 hours ago) Jul 5

to vim/vim, Subscribed

mao-yining left a comment (vim/vim#20714)

Both works there just fine.

Well $WSLENV is also being set on my WIndows Terminal.

I guess it may be caused by docker on win32? Any way $WSL_DISTRO_NAME is a better method isn't it?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.

Maxim Kim

unread,

Jul 5, 2026, 9:00:01 AM (18 hours ago) Jul 5

to vim/vim, Subscribed

habamax left a comment (vim/vim#20714)

Both works there just fine.

Well $WSLENV is also being set in cmd.exe on my WIndows Terminal.

I guess it may be caused by docker on win32? Any way $WSL_DISTRO_NAME is a better method isn't it?

It might be better, idk. For what I know, it is set ($WSLENV) for my debian WSL in the windows terminal and is not set for cmd.exe in the same windows terminal.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.

Maxim Kim

unread,

Jul 5, 2026, 8:51:49 PM (6 hours ago) Jul 5

to vim/vim, Subscribed

habamax left a comment (vim/vim#20714)

Both works there just fine.

Well $WSLENV is also being set in cmd.exe on my WIndows Terminal.

I guess it may be caused by docker on win32? Any way $WSL_DISTRO_NAME is a better method isn't it?

I take it back, I didn't test it properly -- you're right $WSLENV is set in cmd.exe inside windows terminal.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.

Reply all

Reply to author

Forward