From: "Sébastien Kirche" <sebastien.kirche@sage.com>
Subject: Re: Auto load at startup
Date: Tue, 14 Oct 2003 10:43:42 +0200 [thread overview]
Message-ID: <83CA5165-FE22-11D7-A6A2-000393861220@sage.com> (raw)
In-Reply-To: <3F8AE45A.7080606@yahoo.com>
Le lundi, 13 oct 2003, à 19:43 Europe/Paris, Kevin Rodgers a écrit :
>> I tried this tip that seems to work, but I would like to understand
>> why the subdirs.el fails/isn't sufficient.
>
> What exactly did you put in ~/.my_elisp_dir/subdirs.el that didn't
> work?
Well,
actually, i think after investigation that I could have fixed my
problem.
It was mainly a mis-understand of behaviour of emacs about the
load-path :
i first added the following in my .emacs :
,----
| (if (file-exists-p "~/.elisp/" )
| (setq load-path (cons (concat "~/.elisp/" ) load-path))
| )
`----
and that subdirs.el in ~/.elisp :
,----
| (if (fboundp 'normal-top-level-add-subdirs-to-load-path)
| (normal-top-level-add-subdirs-to-load-path))
`----
the lisp files that were in ~/.elisp were accessible, but i found that
packages in subdirs were accessibles but not pre-loaded, that was what
i mis-understood.
I corrected the following like this :
,----
| ; check either Emacs or XEmacs
| (defvar is-xemacs
| (string-match "XEmacs" emacs-version)
| "Variable interne differente de nil si on est dans XEmacs"
| )
|
| ; add my personal elisp directory to search path + preload
| (defvar my-elisp-path "~/.elisp" "Chemin vers mes packages elisp")
| (if is-xemacs
| (setq my-elisp-path (expand-file-name my-elisp-path))
| )
| (add-to-list 'load-path my-elisp-path)
| (progn (cd my-elisp-path) (normal-top-level-add-subdirs-to-load-path))
`----
What do you think of that proposition ?
Thanks for any remark
Sébastien.
next prev parent reply other threads:[~2003-10-14 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1597.1066056301.21628.help-gnu-emacs@gnu.org>
2003-10-13 17:43 ` Auto load at startup Kevin Rodgers
2003-10-14 8:43 ` Sébastien Kirche [this message]
2003-10-13 14:43 Sébastien Kirche
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=83CA5165-FE22-11D7-A6A2-000393861220@sage.com \
--to=sebastien.kirche@sage.com \
/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).