From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, Sun Yijiang <sunyijiang@gmail.com>,
emacs-devel@gnu.org
Subject: Re: What about a seperate "HOME" environment variable under w32?
Date: Wed, 27 Apr 2005 14:59:04 -0400 [thread overview]
Message-ID: <m1zmvkaw1h.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <426FD1D5.2090104@gnu.org> (Jason Rumney's message of "Wed, 27 Apr 2005 18:54:29 +0100")
> If HOME is not set as an environment variable on w32, Emacs will read it
> from the registry (also used as the equivalent of .Xdefaults). Perhaps we
> could change the priority of these, so that the registry overrides the
> environment, since users are unlikely to set a specific HOME for Emacs in
> the registry and then expect to override it by changing their environment.
Until someone actually shows us some concrete scenario where the current
behavior is a problem, I don't see any need to change anything and I don't
think making blind changes like that would help much either.
I for one occasionally like to change my HOME envvar for a particular
process, typically to make sure no other ~/.foo file influences
the behavior, or as a user-level variant of chrooting. Of course, it's
typically under GNU/Linux, so it may not be pertinent for w32.
Stefan
next prev parent reply other threads:[~2005-04-27 18:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 12:08 What about a seperate "HOME" environment variable under w32? Sun Yijiang
2005-04-25 15:35 ` Benjamin Riefenstahl
2005-04-25 16:34 ` Eli Zaretskii
2005-04-25 17:04 ` David Kastrup
2005-04-25 18:15 ` Eli Zaretskii
2005-04-25 18:26 ` David Kastrup
2005-04-25 20:59 ` Eli Zaretskii
2005-04-25 21:06 ` David Kastrup
2005-04-27 17:54 ` Jason Rumney
2005-04-27 18:59 ` Stefan Monnier [this message]
2005-04-25 18:56 ` Stefan Monnier
2005-04-25 21:27 ` Lennart Borgman
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=m1zmvkaw1h.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sunyijiang@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 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).