Re: 21.5-b26: autoloads already loaded errors?

Raymond> Is this expected behavior. sjt> No. What does M-x list-load-path-shadows have to say? Raymond> M-x list-load-path-shadows says: [ perfectly normal-looking shadows removed ] OK, that's working correctly. Do you build your personal pcl-cvs using the XEmacs package framework, or do you just byte-compile all the files and stick them in the right place? Raymond> I see I have a few more shadows than I thought. Are they packages that you use frequently? Do they also produce autoloads warnings? Raymond> 21.5-b25 didn't complain, and I definitely haven't Raymond> changed anything since installing 21.5-b26. What does Raymond> "play tricks" with load-paths mean? I haven't changed Raymond> that in a long time either. "Play tricks" means using setq, add-to-list, etc on the load-path variable. It's very unusual nowadays, but there could theoretically be something left over from your .emacs of the age of Emacs 18.55 or so.:-) There's been a bit of configure hacking since 21.5.25. The only thing that looks remotely plausible would be Jerry James's "autoconf 2.59 political correctness" patch, but that shouldn't change any semantics. Mike Sperber's package configuration patch was added in 21.5.25. Do you use any package-path configuration (specifically --package-prefix or the now-obsolete --package-path) in your configure? Raymond> Oh, yes, I forget to mention that the first thing I tried Raymond> was xemacs -vanilla. This, of course, produces no Raymond> warnings. If I click the menu item to load my init Raymond> files, it stops with an error that it can't load one of Raymond> my personal el files. This, naturally, doesn't happen Raymond> when I leave off the -vanilla. That's very strange. Please send a bug report with M-x report-xemacs-bug, and also the contents of that error message about your personal file. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.