Repository navigation
Launch Windows diff tools from inside WSL - #949
Merged
Merged
Conversation
A tool with no copy in the distribution is resolved from its Windows definition and started through WSL's interop, with both files passed as Windows paths. Such a tool is found again by its command line and is never killed from here, since the process this side holds is WSL's stand-in for it. DiffEngine_WslWindowsTools=false turns it off.
# Conflicts: # readme.md # readme.source.md
This was referenced Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #947, which stops WSL counting as a build server. Without that, nothing is launched inside WSL at all.
Inside a WSL distribution, a tool with no copy in the distribution is now resolved from its Windows definition and started through WSL's interop. Both files are passed as Windows paths:
C:\...on a mounted drive,\wsl.localhost\<distro>\...otherwise.How
OsSettingsResolver,WslHost): the Linux definition first, then the Windows one. The host's variables come from onecmd.exe /u /c set, its drives from/proc/mounts, the share name from onewslpath -w /. A program on the PATH is found from one listing of each host directory, since a stat on a Windows drive from inside WSL is most of a millisecond.WslPaths): translated in process.WslInterop.Start): all three streams redirected and closed, so the tool does not hold the pipedotnet testreads.pslists such a tool as/init <exe> <exe> <args>, whichStripProxybrings back to the command it was started with.Behaviour to know
.cmd, and Vim and Neovim.DiffEngine_WslWindowsTools=falseturns it off.Testing