From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: puzzled with load-path entries - where do they come from when .emacs is empty?
Date: Mon, 10 Nov 2008 20:45:21 -0700 [thread overview]
Message-ID: <gfav4g$up1$1@ger.gmane.org> (raw)
In-Reply-To: <1fcacf3d-32af-464e-b117-fa0669dd790d@i24g2000prf.googlegroups.com>
Mirko wrote:
> I found site-lisp/site-start.d with auctex.el and preview-latex.el.
> That explains the auctex message during startup. But still no clue as
> to where load-path gets preloaded.
>
> Actually, could it be that emacs populates load-path automatically
> based on the contents of the site-lisp directory? That would explain
> everything.
See the "Startup Summary" node of the Emacs Lisp manual:
| The order of operations performed (in `startup.el') by Emacs when it is
| started up is as follows:
|
| 1. It adds subdirectories to `load-path', by running the file named
| `subdirs.el' in each directory in the list. Normally this file
| adds the directory's subdirectories to the list, and these will be
| scanned in their turn. The files `subdirs.el' are normally
| generated automatically by Emacs installation.
To see how load-path is initialized while building Emacs, see the
Makefile (itself generated from Makefile.in by configure):
| # Where to install the lisp files distributed with
| # Emacs. This includes the Emacs version, so that the
| # lisp files for different versions of Emacs will install
| # themselves in separate directories.
| lispdir=${datadir}/emacs/${version}/lisp
|
| # Directories Emacs should search for lisp files specific
| # to this site (i.e. customizations), before consulting
| # ${lispdir}. This should be a colon-separated list of
| # directories.
|
locallisppath=${datadir}/emacs/${version}/site-lisp:${datadir}/emacs/site-lisp
|
| # Where Emacs will search to find its lisp files. Before
| # changing this, check to see if your purpose wouldn't
| # better be served by changing locallisppath. This
| # should be a colon-separated list of directories.
| lisppath=${locallisppath}:${lispdir}:${datadir}/emacs/${version}/leim
--
Kevin Rodgers
Denver, Colorado, USA
prev parent reply other threads:[~2008-11-11 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 17:10 puzzled with load-path entries - where do they come from when .emacs is empty? Mirko
2008-11-10 18:59 ` Mirko
2008-11-10 19:33 ` Mirko
2008-11-11 0:08 ` Xah
2008-11-11 21:45 ` Mirko
2008-11-11 3:45 ` Kevin Rodgers [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='gfav4g$up1$1@ger.gmane.org' \
--to=kevin.d.rodgers@gmail.com \
--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).