By default, the former includes all, bloating PATH with Intel, FUJITSU, Roxio, MS’s OpenSSH, etc, but also windows ports of pandoc, go, certbot, etc which I want on PATH. Check with ORIGINAL_PATH.
The latter by default includes none (a few), the few in ORIGINAL_PATH, ie, windows system and powershell paths, and perl (why perl?).
It then prepends its environment dirs to PATH.
Perhaps systemd management of envars is a good idea ¯(ツ)/¯
I didn’t realize most of the apps I’m now calling are from MSYS2 packages, except for the haskell ones. But I was surprised lean wasn’t on PATH when I saw the installer say it was adding a regedit entry for it, but that I may have to open a new shell terminal.
Oh, well. One more entry in MSYS2’s bash_profile, the ~/.elan/bin one, along with the haskell, go and lua-language-server ones.
The lua one shouldn’t need to be in bash_profile? No I see it was installed from github, the files there need to be in the same dir as the executable and it’s not from a MSYS2 package.
Me atBack to EnvVarsOnWindows
Back to HomePage