|--==> "IM" == Istvan Marko writes: IM> "Steven E. Harris" writes: >>Steve Youngs writes: >> >>>Why isn't your Gnus autoloading? Back in October last year I tweaked >>>the build so `auto-autoloads.el' & `custom-load.el' are created when >>>building with XEmacs. Isn't it working for you? >> >>I use a Gnus built from CVS and stored under ~/usr/local, so I don't >>have the Gnus package installed. If I start up XEmacs without loading >>Gnus explicitly, it doesn't know the functions `gnus' or >>`gnus-no-server.' Should it? Does auto-autoloads.el provide these >>functions? IM> (require 'gnus-load) ; setup the gnus autoloads In XEmacs, this shouldn't be needed because of auto-autoloads.el which is loaded automatically at XEmacs start (providing it is in the default load-path). Another thing to consider... (insert-file-contents (locate-library "gnus-load.el")) (provide 'gnus-load) ;;; Local Variables: ;;; version-control: never ;;; no-byte-compile: t ;;; no-update-autoloads: t ;;; End: ;;; gnus-load.el ends here It isn't going to load much. :-) Yes, I did this intentionally. The best way to load Gnus in XEmacs is to have it installed in a default package path [1], and then do nothing except start XEmacs. Footnotes: [1] In search order: ~/.xemacs/site-packages ~/.xemacs/mule-packages ~/.xemacs/xemacs-packages /lib/xemacs/site-packages [2] /lib/xemacs/mule-packages /lib/xemacs/xemacs-packages [2] This is the default if you don't give configure any path options when building Gnus. -- |---------------------| | Ashes to ashes, dust to dust. | | The proof of the pudding, is under the crust. | |---------------------------------|