From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Location of .emacs in Windows 7
Date: Sun, 18 Jan 2015 18:41:18 +0200 [thread overview]
Message-ID: <83d26cyrbl.fsf@gnu.org> (raw)
In-Reply-To: <87mw5gyroz.fsf@gmail.com>
> From: Jordan Wilson <inopem@gmail.com>
> Date: Sun, 18 Jan 2015 16:33:16 +0000
>
> There's a file in the Emacs distribution (it's
> share/emacs/site-lisp/site-start.el in 24.4 from ftp.gnu.org, it might
> be in a different place on other versions) that allows you to define HOME,
> i.e. what `~' expands to.
IME, it's not a good idea to define HOME (or PATH or ...) inside Emacs
differently than it's defined outside, because it will cause subtle
problems, e.g. in programs not invoked from Emacs. It is best to
define HOME in the environment outside Emacs, such that both Emacs and
the other programs use the same value.
prev parent reply other threads:[~2015-01-18 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 0:38 Location of .emacs in Windows 7 Steve Graham
2015-01-17 2:02 ` Óscar Fuentes
2015-01-17 2:12 ` Marcin Borkowski
2015-01-18 16:33 ` Jordan Wilson
2015-01-18 16:41 ` Eli Zaretskii [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=83d26cyrbl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).