From: Jason Rumney <jasonr@gnu.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Some findings and suggestion about Emacs on w32
Date: Sat, 23 Oct 2004 18:39:45 +0100 [thread overview]
Message-ID: <uvfd12v1a.fsf@jasonrumney.net> (raw)
In-Reply-To: <m36551ehcq.fsf@seneca.benny.turtle-trading.net> (Benjamin Riefenstahl's message of "Sat, 23 Oct 2004 14:42:13 +0200")
Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de> writes:
> Isn't the opposite the case? When "emacs_dir" is not set it is
> automatically replaced with a generated value.
emacs_dir is always replaced with the generated value. The only time
it is not is if Emacs can't work out what the generated value should
be (you have installed in a non-standard directory).
The other values in the registry are the same as the defaults. Emacs
will actually work now with nothing in the registry, the main reason
for setting them in the install program is that older versions used
hard-coded paths (not relative to emacs_dir), which may cause
problems if they point to a different version, so we want to replace
the old values.
next prev parent reply other threads:[~2004-10-23 17:39 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 22:24 Some findings and suggestion about Emacs on w32 Lennart Borgman
2004-10-22 23:47 ` Kim F. Storm
2004-10-23 13:01 ` Lennart Borgman
2004-10-24 22:23 ` Kim F. Storm
2004-10-24 22:44 ` Stefan
2004-10-24 22:58 ` Guy Gascoigne-Piggford
2004-10-24 23:36 ` Stefan
2004-10-24 23:44 ` Lennart Borgman
2004-10-24 22:57 ` Guy Gascoigne-Piggford
2004-10-25 7:13 ` David Kastrup
2004-10-25 8:13 ` Kim F. Storm
2004-10-25 16:50 ` Lennart Borgman
[not found] ` <m3sm 81q3ut.fsf@kfs-l.imdomain.dk>
2004-10-26 8:29 ` Kim F. Storm
2004-10-26 17:29 ` Lennart Borgman
2004-10-26 17:43 ` Jason Rumney
2004-10-26 17:54 ` Stephan Stahl
2004-10-26 17:58 ` Lennart Borgman
2004-10-26 21:59 ` Kim F. Storm
2004-10-26 23:03 ` Lennart Borgman
2004-10-26 17:55 ` Lennart Borgman
2004-10-26 18:50 ` Guy Gascoigne - Piggford
2004-10-26 20:48 ` Lennart Borgman
2004-10-23 12:42 ` Benjamin Riefenstahl
2004-10-23 13:15 ` Lennart Borgman
2004-10-23 13:40 ` Benjamin Riefenstahl
2004-10-23 17:39 ` Jason Rumney [this message]
2004-10-24 18:39 ` Benjamin Riefenstahl
2004-10-24 20:02 ` Jason Rumney
2004-10-24 20:25 ` Lennart Borgman
2004-10-24 20:43 ` Jason Rumney
2004-10-24 22:01 ` Guy Gascoigne-Piggford
2004-10-23 13:54 ` Richard Stallman
2004-10-23 17:44 ` Jason Rumney
2004-10-23 18:58 ` Guy Gascoigne-Piggford
2004-10-24 1:17 ` Lennart Borgman
2004-10-24 12:14 ` Jason Rumney
2004-10-24 12:46 ` Kim F. Storm
2004-10-25 4:30 ` Dhruva Krishnamurthy
2004-10-25 20:28 ` Lennart Borgman
2004-10-24 22:06 ` Stefan
2004-10-25 8:42 ` Kim F. Storm
2004-10-25 9:00 ` Guy Gascoigne-Piggford
2004-10-25 9:29 ` Kim F. Storm
2004-10-25 10:42 ` Dhruva Krishnamurthy
2004-10-25 11:39 ` Stefan
2004-10-25 12:06 ` Kim F. Storm
2004-10-25 12:25 ` Stefan
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=uvfd12v1a.fsf@jasonrumney.net \
--to=jasonr@gnu.org \
--cc=emacs-devel@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.
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).