Invalid PWD after cmd.exe => msys.cmd

[drizt]

Description / Steps to reproduce the issue

1. Run cmd.exe
2. Set initial PWD. set PWD=%CD%
3. Run msys2.cmd from cmd.exe
4. Check PWD with pwd or echo $PWD

Expected behavior

Unix path starting with /c/...

Actual behavior

Windows path starting with C:\...

Verification

• I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)

Windows Version

MSYS_NT-10.0-19045

Are you willing to submit a PR?

No response

[drizt]

My exact problem. I use nvm in .bashrc and gsudo from scoop. nvm internally uses $PWD in some loop. When $PWD invalid loop hangs. So when I do sudo in my terminal it hangs because after sudo $PWD has mixed style. sudo is win app so after starting it $PWD looks like C:/Users/taurus. Then sudo starts msys. msys doesn't fix this var.

[drizt]

diff --git a/winsup/cygwin/environ.cc b/winsup/cygwin/environ.cc
index 4e049211e..985730034 100644
--- a/winsup/cygwin/environ.cc
+++ b/winsup/cygwin/environ.cc
@@ -323,6 +323,7 @@ static win_env conv_envvars[] =
   {
     {NL ("PATH="), NULL, NULL, env_PATH_to_posix, env_plist_to_win32, true},
     {NL ("HOME="), NULL, NULL, env_path_to_posix, env_path_to_win32, false},
+    {NL ("PWD="), NULL, NULL, env_path_to_posix, env_path_to_win32, false},
     {NL ("LD_LIBRARY_PATH="), NULL, NULL,
                               env_plist_to_posix, env_plist_to_win32, true},
     {NL ("ORIGINAL_PATH="), NULL, NULL, env_PATH_to_posix, env_plist_to_win32, true},

Probably this patch will be enough to fix problem. Not tested. I haven't any msys compilation experience.