Manoj Srivastava <[EMAIL PROTECTED]> wrote: > On Sun, 10 Aug 2003 Peter S Galbraith <[EMAIL PROTECTED]> said: > > > Hi all, I wondering about load-path bloat and whether it matters. > > > http://bugs.debian.org/189754 said that when help was listed about a > > function of mine, the user couldn't click on the function name to > > move point to the source code. > > > That's because I add the compiled lisp directory to to load-path, > > but not the directory of the sources themselves. > > I add both; the compiled ones at the front of the laod path, > and the sources at the tail, like so: > ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; > (if (fboundp 'debian-pkg-add-load-path-item) > (setq load-path (debian-pkg-add-load-path-item (concat "/usr/share/" > (symbol-name > debian-emacs-flavor) > "/site-lisp/gnus"))) > (setq load-path (cons (concat "/usr/share/" > (symbol-name debian-emacs-flavor) > "/site-lisp/gnus") load-path))) > ;; Make sure that the uncompiled files are also in the > ;; laod-path, though near the end. > (setq load-path (nconc load-path > (list "/usr/share/emacs/site-lisp/gnus/lisp"))) > ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
I'm been using this since, but have a new problem. My package provides ibuffer.el but XEmacs already has one of those. Even if I skip byte-compiling it for XEmacs, the directory "/usr/share/emacs/site-lisp/emacs-goodies-el" appears _before_ "/usr/share/xemacs21/xemacs-packages/lisp/ibuffer" in the load-path. I guess XEmacs fill-out its load-path only later on.emacs-goodies-el. It appears to be the same case in Emacs as well. So how do we make sure the source load-path really appear at the end? Thanks for ideas, Peter
