From: Baloff <washdc@wash.edu>
Subject: order of search in load-path
Date: 04 Sep 2005 09:50:24 +1000 [thread overview]
Message-ID: <87y86d7ltr.fsf@wash.edu> (raw)
Hello
I learned that emacs searches directly in the order in which they
appear in load-path, the first 2 items in my case is
load-path's value is
("/usr/independ_packages/cedet-1.0pre3/common/icons"
"/usr/independ_packages/cedet-1.0pre3/semantic/wisent"
...
isn't better that it searches its default Lisp directly first. and if
so, is this variable customizable and where?
I could (setq load-path (cons or append "some/path//lisp" load-path)) but this
is the main thing I am trying to avoid, playing around with .emacs to
move items around in load-path variable.
second point:
I do not have any statement in my .emacs which adds/appends to the
load-path. how did the current value happened to have those 2 items
first in the list?
in that variable, I must have more than 20 paths, is that ok, or need
to collect all whose ".el" in fewer dirs and load those only?
thanks
> LocalWords: setq ok dirs
next reply other threads:[~2005-09-03 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-03 23:50 Baloff [this message]
2005-09-04 5:05 ` order of search in load-path Tim X
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=87y86d7ltr.fsf@wash.edu \
--to=washdc@wash.edu \
/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).