Re: Extant autoloads?

kkm> Dumped lisp files are not supposed to contribute to autoloads, no? kkm> I am getting this: kkm> "..\lib-src\i" "..\src\xemacs.exe" -vanilla -batch -l autoload -f kkm> batch- kkm> update-one-directory ..\lisp -f batch-byte-compile-one-file kkm> ..\lisp\auto-autoloa kkm> ds.el -l cus-dep -f Custom-make-dependencies ..\lisp kkm> Updating autoloads in directory e:\xemacs\xemacs\lisp... kkm> No autoloads found in lisp/custom-load.el kkm> No autoloads found in lisp/printer.el kkm> No autoloads found in lisp/printer.el kkm> printer.el is a dumped file. Should it be searched for autoloads, really? kkm> Should it be searched for autoloads *twice*? I just do not know where to kkm> control this kind of behavior. Well, it's just an optimization to not have autoloads for dumped files. Autoloads do not override "real" definitions. One can imagine different builds of XEmacs with different dumped lisp. For example, a dumped file could do (when (featurep 'FOO) (load "FOO")) so in general, the dumped lisp file set is dependent on configure-time options. So it might not be worth optimizing away the dumped-lisp autoloads - and this is only one directory of 89 (!), so you don't save much performance-wise. (length load-path) ==> 89 But of course, the double autoloads should go. No idea where those came from.