From: Dan Nicolaescu <dann@gnu.org>
To: emacs-devel@gnu.org
Subject: running ./temacs
Date: Wed, 17 Nov 2010 01:57:10 -0500 [thread overview]
Message-ID: <yxq8w0ssaih.fsf@fencepost.gnu.org> (raw)
Running just ./temacs is currently not very useful.
The first think it does when starting up is complain that /.emacs.d/ cannot be found.
M-: (getenv "HOME")
return nil
This is because `process-environment' is nil.
emacs.c contains this code:
/* Initialize and GC-protect Vinitial_environment and
Vprocess_environment before set_initial_environment fills them
in. */
if (!initialized)
syms_of_callproc ();
/* egetenv is a pretty low-level facility, which may get called in
many circumstances; it seems flimsy to put off initializing it
until calling init_callproc. */
set_initial_environment ();
The first comment above seems to be contradicted by the code in
set_initial_environment that only initializes Vprocess_environment if
`initialized' is true (which is not when running just ./temacs):
void
set_initial_environment (void)
{
register char **envp;
#ifdef CANNOT_DUMP
Vprocess_environment = Qnil;
#else
if (initialized)
#endif
{
for (envp = environ; *envp; envp++)
Vprocess_environment = Fcons (build_string (*envp),
Vprocess_environment);
/* Ideally, the `copy' shouldn't be necessary, but it seems it's frequent
to use `delete' and friends on process-environment. */
Vinitial_environment = Fcopy_sequence (Vprocess_environment);
}
}
What is the intention here?
[Hacking around this so that Vprocess_environment is initialized when
not dumping makes ./temacs work correctly]
next reply other threads:[~2010-11-17 6:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 6:57 Dan Nicolaescu [this message]
2010-11-17 7:43 ` running ./temacs Óscar Fuentes
2010-11-18 4:44 ` Dan Nicolaescu
2010-11-18 14:26 ` Stefan Monnier
2010-11-18 21:20 ` Dan Nicolaescu
2010-11-18 22:17 ` Stefan Monnier
2010-11-18 22:19 ` Dan Nicolaescu
2010-11-19 7:51 ` Eli Zaretskii
2010-11-20 7:28 ` Dan Nicolaescu
2010-11-21 5:48 ` Stefan Monnier
2011-05-31 5:19 ` Dan Nicolaescu
2011-05-31 6:36 ` Dan Nicolaescu
2011-05-31 6:47 ` Eli Zaretskii
2011-05-31 6:55 ` Dan Nicolaescu
2011-05-31 8:44 ` Eli Zaretskii
2011-05-31 14:53 ` Dan Nicolaescu
2011-05-31 6:40 ` Eli Zaretskii
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=yxq8w0ssaih.fsf@fencepost.gnu.org \
--to=dann@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).