On Thursday, 15 August 2002, Stephen J. Turnbull wrote:
Mike, do you have any comments?
>>>>> "Ray" == Raymond Toy <toy(a)rtp.ericsson.se> writes:
Ray> Uhh, wait. What am I volunteering to delete here? :-) I
Ray> guess that was ~/.xemacs from my load-path.
Ray> Then where am I supposed to put my own stuff like my
Ray> personalized versions and modifications of existing stuff?
Baroque, I know, but initialization will pick that up automatically
and stick it in load-path. If you have an auto-autoloads file there,
it will pick it up automatically:
xemacs -batch -vanilla -l autoload -f batch-update-directory \
should create it for you (of course, you have to put the appropriate
autoload cookies in the files).
Note that autoloads will possibly get you in trouble if you have a
personalized version of a library available elsewhere on load-path.
Now this confuses me. How will having another version of the library
available elsewhere affect autoload ? I thought that autoload means just
that: automatically load the needed libraries by searching through
load-path. Since ~/.xemacs/xemacs-packages/lisp/ should come much earlier
than other paths, why would autoload not pick-up these versions and ignore
the versions seen later in the load-path ?
Krishnakumar B <kitty at cs dot wustl dot edu>
Distributed Object Computing Laboratory, Washington University in St.Louis