Re: relative load-file

[Tassilo Horn <tassilo@member.fsf.org>]

Rocky Bernstein <rocky@gnu.org> writes:

Hi Rocky,

> I don't see that this does what I need or meant to convey:
>    one wants to load an Emacs Lisp file *relative [to] the* *[directory of
> the]* *file that issues the load *
>
> Here my test of the above suggestion..
>
> $ find /tmp/proj -type f -print -exec cat {} \;
> /tmp/proj/subdir/subload.el
>        (load-file "../test1.el")
> /tmp/proj/test1.el
>       (load-file "test3.el")
> /tmp/proj/test3.el
>        (message "test3 here")
>
> Now inside emacs I edit /tmp/proj/subdir/subload.el, and M-x
> eval-current-buffer. I get:
>
> load-file: Cannot open load file: /tmp/proj/subdir/test3.el
>
> This is loading relative to the directory I started at,
> /tmp/proj/subdir, not relative to the directory that of the file that
> issued the load, /tmp/proj/test1.el.

I see.  Well, generally those problems don't occur, because all elisp
projects I know put all the *.el files into one directory, and the files
are all named proj-xxx.el with one proj.el.  This prefixing is kind of a
convention (not only for files, but vars and funs, too), because there
are no namspaces in elisp.

Emacs itself has some subdirs, but all of them are added to the
load-path.  In both cases, the usual provide/require mechanics suffice.

Bye,
Tassilo