I'm using msys2 bash 4.3.26 (i686-pc-msys) on Windows, and recently I find that it breaks my pscp and scp (msys1):
When I run pscp req.py hostname:/home/user/xxx/yyy/:
msyswill change the second args tohostname;D:\msys\home\user\xxx\yyy\- and then
pscpwill report:ssh_init: Host does not exist - my
scpwhich is from msys-1.0 (I once used git-for-windows 1.9) reportsssh: Could not resolve hostnamehostname;d: no address associated with name
This is annoying and I have to open cmd.exe to use pscp. Is there any way to prevent MSYS 2 from convert special args?
- I tried wrapping an arg in
'or"and failed - http://www.mingw.org/wiki/Posix_path_conversion is not helpful but disappointing
- environment: Windows 10 Insider x64 and msys2 i686
- the official
scp.exein the same package ofmsys2works well
BTW, this problem only occurs on those .exe files which does not use msys2 DLLs. How this difference is being checked?