From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: emacs-devel@gnu.org, npostavs@users.sourceforge.net
Subject: Re: Emacs 25.2, win64, env vars
Date: Tue, 11 Jul 2017 19:30:42 +0300 [thread overview]
Message-ID: <83y3rvhr65.fsf@gnu.org> (raw)
In-Reply-To: <CAFgFV9N-5uHZwTymS-sW4ZJ6oZyonp0Zd13LJK59adBfhDz-4w@mail.gmail.com> (message from Fabrice Popineau on Tue, 11 Jul 2017 18:24:15 +0200)
> 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>
>
> If so, does it mean that after
> invoking 'setenv', your process-environment has 2 members which both
> start with "TEMP=", but have different values? Because _this_ is what
> I cannot reproduce and frankly don't understand how could it happen.
>
> 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.
Can you tell the details of how it "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.
Maybe we can fix that use case as well, if we understand it well
enough.
next prev parent reply other threads:[~2017-07-11 16:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 20:33 Emacs 25.2, win64, env vars Fabrice Popineau
2017-06-11 21:33 ` Noam Postavsky
2017-06-12 4:40 ` Fabrice Popineau
2017-07-10 17:08 ` Eli Zaretskii
2017-07-11 9:17 ` Fabrice Popineau
2017-07-11 14:31 ` Noam Postavsky
2017-07-11 14:43 ` Eli Zaretskii
2017-07-11 16:24 ` Fabrice Popineau
2017-07-11 16:30 ` Eli Zaretskii [this message]
2017-07-11 18:48 ` Fabrice Popineau
2017-07-22 7:07 ` Eli Zaretskii
2017-07-22 20:02 ` Fabrice Popineau
2017-07-23 14:48 ` Eli Zaretskii
2017-07-24 20:34 ` Fabrice Popineau
2017-07-24 21:20 ` Noam Postavsky
2017-07-25 14:16 ` Eli Zaretskii
2017-07-27 16:35 ` Fabrice Popineau
2017-07-27 16:48 ` Stefan Monnier
2017-07-27 18:54 ` Óscar Fuentes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y3rvhr65.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fabrice.popineau@gmail.com \
--cc=npostavs@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).