I share their distaste for polluting PATH with too many permanent entries, it exposes you to potential incompatibilities between software that requires different versions or configurations of common sets of dependencies. I am a fan of modifying PATH only temporarily and only for the task at hand.
(and Tim Holy deserves all of the credit for Immerse, I just had a trivial one-line patch to make it work better on Windows) On Wednesday, December 16, 2015 at 10:34:21 AM UTC-8, hustf wrote: > > That's a good way to explaining why most shell commands don't work, and I > can adjust accordingly and move on. > > I seem to be limited to running just the .exe-files in c:\windows\ and > ~\system32. Luckily, 'cmd.exe' (and where.exe) is among them, so I can make > do by prefixing some commands with 'cmd'. > > Since this is not widely reported by other users, I suppose either my PATH > must be larger than most - or it's not a popular feature with windows users. > > http://sourceforge.net/p/msys2/wiki/MSYS2%20introduction/ > > *When using the shells, try to remove as many entries from PATH as you > can, ideally only leaving something like C:\Windows\system32. Mixing in > programs from other MSYS2 installations, Cygwin installations or compiler > toolchains is not supported and will probably break things in unexpected > ways. Do not have these things in PATH when running MSYS2 unless you know > exactly what you're doing.* > >
