[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs 25.2, win64, env vars

From: Fabrice Popineau
Subject: Re: Emacs 25.2, win64, env vars
Date: Mon, 24 Jul 2017 22:34:20 +0200

2017-07-23 16:48 GMT+02:00 Eli Zaretskii <address@hidden>:
> From: Fabrice Popineau <address@hidden>
> Date: Sat, 22 Jul 2017 22:02:03 +0200
> Cc: Noam Postavsky <address@hiddennet>, Emacs developers <address@hidden>
>  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.

Sorry, it's probably my misunderstanding.

> 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.

So you are saying that MSYS holds two separate environment variables,
one called "temp", the other "TEMP"?  If so, what do native Windows
programs started from such a shell get in their environment?  The
upper-case one? the first one in the order? both? something else?

 Both GetEnvironmentVariable) and getenv() return :


And from the shell :

$ echo $TEMP

$ echo $temp

So they return the win32 path from the value of the upper case variable.

> I would even recommend that emacs inherits from the desktop environment, not the environment from the
> shell that was used to run emacs.

I expect this to break quite a few legitimate use cases.

Maybe (albeit I couldn't name them).

My opinion (but I may well be alone)  is that Emacs/win32 fiddles too much with those unix-like environments.
This works most of the time, but it also sometimes creates surprising situations.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]