unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Emacs 25.2, win64, env vars
Date: Thu, 27 Jul 2017 20:54:38 +0200	[thread overview]
Message-ID: <874ltxd829.fsf@wanadoo.es> (raw)
In-Reply-To: CAFgFV9MeOqmb72-o24MiTJoWkRUcbt82uxYpECxhW0TkqnCPtA@mail.gmail.com

Fabrice Popineau <fabrice.popineau@gmail.com> writes:

> 3 - apply the fix I offered (or another equivalent one ?)  because it makes
> the handling of environment variables case symetrical for setenv and
> getenv, and both are case insensitive.

+1

I was affected by this issue. Two hours lost trying to figure out what
the problem was an how to work around it.

There are bug reports all around about other cross-platform projects
which found the same problem. Python, for instance, uppercases all
environment variables on Windows.

Emacs should follow the conventions of the host OS.




      parent reply	other threads:[~2017-07-27 18:54 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
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 [this message]

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=874ltxd829.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@gnu.org \
    /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).