cgw> I've got a working script to trace the require's among all cgw> the various .el files (both in xemacs/lisp and in the cgw> packages). Cool! cgw> Look especially for the string NOBODY... I'm impressed. Four features (by visual scan, not grep) not provided anywhere in our core or packages: t - this is a weakness in your script, at least in bbdb.el it is due to this hack: ;; This nonsense is to get the definition of defsubst loaded in ;; when this file is loaded,without necessarily forcing the ;; compiler to be loaded if we're running in an emacs with ;; bytecomp-runtime.el predumped. We are using `require' as a way ;; to get compile-time evaluation of this form so that this works ;; in the old compiler as well as the new one. (require (progn (provide 't) ; eeeewwww, gross! (condition-case () (if (fboundp 'defsubst) 't ;; If byte-optimize can be loaded, use that. (require 'byte-optimize) 'byte-optimize) ;; otherwise, use the boneheaded version of defsubst. (error 'defsubst)))) ange-ftp, efs-x19.15 - apparent aliases for efs, and I'll bet they are fallbacks if efs isn't found lmenu - dunno what that is. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."