Re: auto-autoloads errors

Didier Verna writes: AFAICS this is bad news that needs to be told. Either it's an XEmacs bug that both xemacs-packages/lisp/foo and site-packages/lisp/foo end up in load-path, and we should fix it, or it's a user bug that the same package ends up in xemacs-packages and site-packages, or it's a community bug where two different packages have the same name (and so get the same auto-autoloads feature). In either of the first two cases, you have a distinct and preventable possibility of incompatible code from different versions getting loaded. In the last case, a whole package is getting shadowed since auto-autoloads and custom-load are the way we communicate the existence of a package to XEmacs at initialization. I may be missing something, but I think we should avoid suppressing these warnings if possible. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta