Re: [Mingw-users] Two bugs(?) in the MSYS shell

[Earnie <ea...@us...>]

> From: Eli Zaretskii [mailto:el...@gn...]
> 
> > From: "Earnie" <ea...@us...>
> > Date: Wed, 18 Mar 2015 13:17:20 -0400
> >
> > > From: Eli Zaretskii
> > > > Date: Wed, 18 Mar 2015 02:24:33 -0700
> > > > From: Greg Jung
> > > >
> > > > Is this the actual path expansion policy? This is not how its laid
> > > > out; path expansion refers to arguments and not to the whole
> > environment.
> > >
> > > It refers to both, AFAIK.  At least that's what I see on my system
> > > with
> > MSYS.
> > >
> >
> > There is a small set of environment variables that are modified by
> > MSYS and those are ones where the environment variable in Windows and
> > POSIX were common, e.g. PATH, and required for operating a POSIX
> environment.
> 
> That's not exactly what I see here.  Observe:
> 
>   $ export FOO=/d/gnu
>   $ /d/usr/bin/env | fgrep FOO
>   FOO=d:/gnu
> 

A better example is:

$ export FOO=/d/foo
$ cmd //c set | findstr FOO
FOO=d:/foo

> ("/d/usr/bin/env.exe" is a MinGW port of GNU 'env'.)  Does MSYS know about
> "$FOO"?  I hope not.

I guess I was just too smart about it back whenever and now think I
shouldn't have done that.  Thanks for the kick in the pants.

Earnie