Autoloading and XEmacs 21.1.8

Autoloading and XEmacs 21.1.8

[G. Todd]

Hello all,

A hard drive died so I took the opportunity to upgrade my emacs to
XEmacs 21.1.8. Now, perhaps due to my limited understanding of the new
package and autoloading system, XEmacs doesn't seem to autoload things
in my load path anymore. 

I'm trying to load the latest gnus from ~/gnus/lisp using things like:

(push (expand-file-name "~/gnus/lisp") load-path)
(setq load-path (cons (expand-file-name "~/gnus/lisp") load-path))

etc. etc.

The files were recompiled with xemacs 21.1.8 and I removed the
existing "gnus" package with the package manager interface (and moved
the directory out of the way). It seems the only way I can get it to
work is using (require) to preload everything but that sort of fattens
up the RAM usage and slows down my startup.

Anyone know what's up?  The "~/gnus" directory is not an xemacs
"package". Do I need one of those (new?)  auto-autoload.el files to
get it to work?  In any case I thought I'd mention this because - here
at least - the instructions included with the Gnus release (which
suggest the above load-path approach) don't work "out of the box".

System Info:

XEmacs 21.1 (patch 8) "Bryce Canyon" [Lucid] (i386-redhat-linux)
Gnus v5.8.2 
egcs-2.91.66
glibc-2.1.2-11
GNU Make version 3.77, by Richard Stallman and Roland McGrath.
GNU ld 2.9.1
automake (GNU automake) 1.4
Autoconf version 2.13
binutils-2.9.1.0.23-6
ldconfig-1.9.5-15

Regards,

G. Todd

Re: Autoloading and XEmacs 21.1.8

[Graham Todd]

>>>>> " " == G Todd <gtodd@equilibrio.qc.ca> writes:

 > A hard drive died so I took the opportunity to upgrade my emacs
 > to XEmacs 21.1.8. Now, perhaps due to my limited understanding
 > of the new package and autoloading system, XEmacs doesn't seem
 > to autoload things in my load path anymore.

 > I'm trying to load the latest gnus from ~/gnus/lisp using
 > things like:

 > (push (expand-file-name "~/gnus/lisp") load-path) (setq
 > load-path (cons (expand-file-name "~/gnus/lisp") load-path))

[snip]

Well ignore this question. I remade the binary RPM and reinstalled it
(again) and autoloads like the one above seem to be working
now. Must've just been a permissions problem somewhere...

Sorry for the noise.

G. Todd