Mike Kupfer writes:
Stephen J. Turnbull wrote:
> Mike Kupfer writes:
> > FWIW, the additional noise in 21.5 is from the addition of a Lisp stack
> > trace for each shadow warning.
>
> Never seen one of those. I can't imagine it was deliberate if it's
> due to an XEmacs change. What does the stack trace say?
Here's a sample message for a single package, copied out of *Warnings* :
(1) (packages/warning) Error in Autoload
/usr/new/share/xemacs/xemacs-packages/lisp/xemacs-devel/auto-autoloads: Already loaded
That's not a "shadow" warning, that's a real error. XEmacs attempted
to load an auto-autoloads library for that package twice. If that
succeeded it would be a very bad thing, because it might stomp all
over changes made to the data of that package (including code, such as
advice) in the time since the first load. On the other hand, it
shouldn't happen without your intervention, because the package
initialization code should refuse to add a shadowed directory to
`load-path'. So the auto-autoloads library itself has to error,
because we can't be sure what you had in mind. (N.B. It is not an
error to explicitly reload a regular library.)
Bottom line, this isn't just an annoyance, something needs to be
fixed. I suspect your installation ;-), but it could be XEmacs.
Do you manipulate load-path in site-start, defaults.el, init.el,
custom.el, or any library loaded from one of those?
Do you manipulate load-path in any private package's auto-autoloads?
Does this happen with -vanilla?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta