From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: simple loaded during startup
Date: Sat, 24 Feb 2007 15:10:22 +0200 [thread overview]
Message-ID: <ufy8vvgzl.fsf@gnu.org> (raw)
In-Reply-To: <200702240059.l1O0xMX1010398@oogie-boogie.ics.uci.edu> (message from Dan Nicolaescu on Fri, 23 Feb 2007 16:59:22 -0800)
> From: Dan Nicolaescu <dann@ics.uci.edu>
> Date: Fri, 23 Feb 2007 16:59:22 -0800
>
> Doing
> strace -o emacs.strace emacs -Q --no-site-file -nw
> and then
> grep simple emacs.strace
>
> shows that "simple" is being loaded during startup. This seems strange
> given that "simple" should be in the dumped image...
> If one deletes all traces of simple.el simple.elc simple.el.gz etc
> then emacs gives a "Wrong type argument: nil" error when starting up.
>
> Does anyone know if loading "simple" at startup is intentional?
Actually, Emacs doesn't _load_ simple.elc (put a breakpoint in Fload,
and you'll never see "simple" being loaded), it only locates it. This
is because startup.el:command-line does this:
;; Convert preloaded file names to absolute.
(let ((lisp-dir
(file-truename
(file-name-directory
(locate-file "simple" load-path
(get-load-suffixes))))))
(Armed with lisp-dir, it then proceeds to convert relative file names
in load-history into absolute file names.)
IOW, we use simple.elc as an indicator where the Lisp files reside on
the file system, which is the value of lisp-dir computed in the above
snippet.
I don't see anything wrong with that. Do you?
next prev parent reply other threads:[~2007-02-24 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 0:59 simple loaded during startup Dan Nicolaescu
2007-02-24 13:10 ` Eli Zaretskii [this message]
2007-02-24 18:57 ` Dan Nicolaescu
2007-02-25 4:05 ` Richard Stallman
2007-02-25 21:16 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2007-02-24 22:00 A Soare
2007-02-25 6:26 ` Stuart D. Herring
2007-02-25 18:39 ` Richard Stallman
2007-02-24 23:07 A Soare
2007-02-25 6:23 ` Stuart D. Herring
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ufy8vvgzl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dann@ics.uci.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.