all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: jporterbugs@gmail.com, 67540@debbugs.gnu.org
Subject: bug#67540: 29.1; Emacs on Windows incorrectly capitalizes some environment variables
Date: Fri, 01 Dec 2023 09:14:09 +0200	[thread overview]
Message-ID: <835y1ibdj2.fsf@gnu.org> (raw)
In-Reply-To: <E5E0D47A-9F09-43F5-8DCC-7D9AFFDA90D5@boostpro.com> (message from Dave Abrahams on Thu, 30 Nov 2023 16:13:03 -0800)

> From: Dave Abrahams <dave@boostpro.com>
> Date: Thu, 30 Nov 2023 16:13:03 -0800
> Cc: Jim Porter <jporterbugs@gmail.com>,
>  67540@debbugs.gnu.org
> 
>  It might be nice for Emacs to preserve the case of any existing 
>  environment variables on MS-Windows to be on the safe side though...
> 
>  That's impossible in practice: we'd need to "fix" every single Lisp
>  program and every place in the Emacs C code that compare against
>  "PATH" case-sensitively.  And what about user confusion, for those of
>  us who mostly work on Unix, but sometimes need to work on Windows?
> 
> I don't think this is that hard to fix without breaking anybody.  Simply maintain a mapping of in-Emacs
> upcased environment variable names to the lowercased counterparts from which they came, and
> map back when setting up a process environment.

This will not work reliably, because many programs invoked by Emacs as
sub-processes are ported Unix and GNU/Linux programs, and those expect
PATH, not Path in the environment.





  reply	other threads:[~2023-12-01  7:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30  2:29 bug#67540: 29.1; Emacs on Windows incorrectly capitalizes some environment variables Dave Abrahams
2023-11-30  3:42 ` Jim Porter
2023-11-30  7:22   ` Eli Zaretskii
2023-12-01  0:13     ` Dave Abrahams
2023-12-01  7:14       ` Eli Zaretskii [this message]
2023-12-01 20:34         ` Dave Abrahams
2023-12-02  7:04           ` Eli Zaretskii
2023-12-02 16:22             ` Dave Abrahams
2023-11-30  7:10 ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=835y1ibdj2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67540@debbugs.gnu.org \
    --cc=dave@boostpro.com \
    --cc=jporterbugs@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.