Re: Emacs 25.2, win64, env vars

[Fabrice Popineau <fabrice.popineau@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]

2017-07-22 9:07 GMT+02:00 Eli Zaretskii <eliz@gnu.org>:

> > From: Fabrice Popineau <fabrice.popineau@gmail.com>
> > Date: Tue, 11 Jul 2017 18:24:15 +0200
> > Cc: Noam Postavsky <npostavs@users.sourceforge.net>, Emacs developers <
> emacs-devel@gnu.org>
> >
> > And now I understand the reason why you don't see the problem.
> > I compile emacs from a mingw64 prompt. I have started emacs from the
> msys2 bash.
> > This is what messes up the environment.
> >
> > One one hand, I would say that my proposed fix is harmless and makes
> sure case insensitive search is used
> > for platforms where env vars are supposed to be case insensitive.
> > On the other hand, the problem is the msys2 bash.
>
> Ping!  If we want to fix this problem, please tell the details about
> how the MSYS2 Bash causes it.  If not, let's decide that we don't
> want to fix it.
>

I thought my previous answer was pretty explicit.

MSYS2 bash implements a case sensitive environment, which is different from
the native win32 environment.
If emacs is started from the bash command line, it inherits this
environment.
However this is rather unexpected.
It is hard to tell if a GUI emacs has been started from bash, cmd or from
the desktop.
So the fact that the behaviour is changing accorting to the starting
environment
is annoying.
IMHO and according to the least surprise principle, win32 emacs should
behave as a native app, and not follow this kind of fancy unixy thing.
I would even recommend that emacs inherits from the desktop environment,
not the environment from the shell that was used to run emacs.

Regards,

[-- Attachment #2: Type: text/html, Size: 2337 bytes --]