Stephen J. Turnbull wrote:
That's not a "shadow" warning, that's a real error.
Ah, okay.
Do you manipulate load-path in site-start, defaults.el, init.el,
custom.el, or any library loaded from one of those?
No site-start code. I checked for changes to load-path in my Emacs lisp
library and found one place, but it's in my .emacs. Since I already
have an init.el, I don't think this is the problem. (And commenting out
the load-path hack in .emacs didn't make the startup messages go away.)
Do you manipulate load-path in any private package's
auto-autoloads?
Nope.
Does this happen with -vanilla?
No.
I tried clicking on the "Load init files" button after starting with
-vanilla, and I got an error about being unable to load a library from
my "kupfer-env" XEmacs package. In that case, load-path only refers to
the packages from the sumo (/usr/new/share/.../lisp/pkg1,
/usr/new/share/.../lisp/pkg2, etc). No references to anything in my
.xemacs directory.
Hmm. I tried renaming ~/.xemacs/site-packages and
~/.xemacs/xemacs-packages. That gets me an error on a regular
(non-vanilla) startup (as above, because it couldn't find a library in
the kupfer-env package). I put back just
.xemacs/site-packages/lisp/kupfer-env and got a clean startup. I then
put back .xemacs/site-packages/lisp/mail-lib and got the "already
loaded" error. (It's a slightly hacked version of the standard
mail-lib.)
Okay, let's take kupfer-env out of the picture. I renamed
.xemacs/init.el and .emacs, and I deleted
.xemacs/site-packages/lisp/kupfer-env. And I renamed .xemacs/custom.el
for good measure. But on startup I still get the "already loaded" error
message for mail-lib, with both 21.4 and 21.5.
So I think this is pointing at a problem in the package startup code.
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta