From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: subdirs works for emacs but fails for me -- why?
Date: Tue, 20 Oct 2009 22:13:18 -0600 [thread overview]
Message-ID: <hbm1ou$joi$1@ger.gmane.org> (raw)
In-Reply-To: <mv4optsk8q.fsf@xoc2.stanford.edu>
Glenn Morris wrote:
> rustom wrote:
>
>> When emacs finds such a file it adds the subdirs to the load-path
>> If I put a similar file in my load-path it does not do any good.
>
> subdirs.el is an internal mechanism that by design only works for
> "standard" Emacs directories, not any that you might happen to add to
> load-path (eg in .emacs).
But if one initializes load-path via the EMACSLOADPATH environment variable,
it looks like the subdirs.el trick will work.
>> Also why the fboundp stuff?
>
> Perhaps for compatibility for Emacs versions without this function, eg
> if they happen to share site-lisp directories.
--
Kevin Rodgers
Denver, Colorado, USA
prev parent reply other threads:[~2009-10-21 4:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 17:54 subdirs works for emacs but fails for me -- why? rustom
2009-10-20 23:45 ` Glenn Morris
2009-10-21 4:13 ` 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='hbm1ou$joi$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).