From: Robinows@aol.com
Cc: rdieter@math.unl.edu
Subject: Re: [h-e-w] Re: Emacs-21.3-5 msi installer
Date: Wed, 4 May 2005 22:43:36 EDT [thread overview]
Message-ID: <5b.691a317b.2faae258@aol.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1512 bytes --]
>From help-emacs-windows (a discussion about a Windows installer):
In a message dated 5/4/2005 6:57:24 P.M. Eastern Daylight Time,
rdieter@math.unl.edu writes:
Brian Elmegaard wrote:
>> Works like a charm, Rex.
>>
>> I have the following suggestions to be put in default.el:
>> (setenv "HOME" (getenv "USERPROFILE")) ; users will not have the root
>> ; of C: as home
>What if HOME is already set?
>Wouldn't it be better to set HOME to %HOMEDRIVE%%HOMEPATH% (if >they're
defined)?
Of course, overwriting an existing HOME variable is a bad idea, but Brian
has a point. Naive Windows users are not likely to have a HOME variable and in
a corporate environment may not have write access to C:\. It seems to me the
place to fix this is in Emacs, not in a third-party tool. Something like the
patch below.
This looks first for the HOME variable, then USERPROFILE (likely to be
C:\Documents and Settings\%USERNAME% ), and then, as a last resort, C:/.
One could get fancier by playing with the default value of "emacs_dir" or
using %HOMEDRIVE% instead of C:
--- w32.c.~1.90.~ 2005-02-16 21:28:51.296875000 -0500
+++ w32.c 2005-05-04 20:21:49.593750000 -0400
@@ -949,7 +949,8 @@
char * def_value;
} env_vars[] =
{
- {"HOME", "C:/"},
+ {"USERPROFILE", "C:/"},
+ {"HOME", "%USERPROFILE%"},
{"PRELOAD_WINSOCK", NULL},
{"emacs_dir", "C:/emacs"},
{"EMACSLOADPATH",
"%emacs_dir%/site-lisp;%emacs_dir%/../site-lisp;%emacs_dir%/lisp;%emacs_dir%/leim"},
[-- Attachment #1.2: Type: text/html, Size: 3070 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
reply other threads:[~2005-05-05 2:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5b.691a317b.2faae258@aol.com \
--to=robinows@aol.com \
--cc=rdieter@math.unl.edu \
/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).