unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Subject: Re: What about a seperate "HOME" environment variable under w32?
Date: Mon, 25 Apr 2005 23:27:51 +0200	[thread overview]
Message-ID: <002001c549dd$aa96b250$0200a8c0@sedrcw11488> (raw)
In-Reply-To: 5065e2900504250508506d7640@mail.gmail.com

Please see also the discussion in oct 2004 in the archives about "$HOME
default on w32".


----- Original Message ----- 
From: "Sun Yijiang" <sunyijiang@gmail.com>
To: <emacs-devel@gnu.org>
Sent: Monday, April 25, 2005 2:08 PM
Subject: What about a seperate "HOME" environment variable under w32?


The %HOME% environment variable is used by many programs under w32, so it's
really a mess sometime. I suggest Emacs use a different HOME variable
underw32, something like %EMACS_HOME% or %EHOME%. This can be backward
compatible if Emacs first look for %EHOME% variable, and if not found,
search for %HOME% instead. User can also set simply set %EHOME% to %HOME% to
get backward compatibility.
 Sun Yijiang



----------------------------------------------------------------------------
----


> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel

      parent reply	other threads:[~2005-04-25 21:27 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
2005-04-25 18:56 ` Stefan Monnier
2005-04-25 21:27 ` Lennart Borgman [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='002001c549dd$aa96b250$0200a8c0@sedrcw11488' \
    --to=lennart.borgman.073@student.lu.se \
    /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).