<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear all:<div><br></div><div>I have recently installed the port xemacs @21.4.22_11 on two different machines, and am having trouble with load path shadowing, which I don't find mentioned anywhere in either bug lists or mailing lists.</div><div><br></div><div>One machine is an older mini (mid 2011) running Lion, and this xemacs is an upgrade from 21.4.22_9. All earlier versions are inactive, and I cannot activate them without forcing due to a ctags 5.8.2 dependency.</div><div><br></div><div>The other machine is a new (clean) 2015 macbook pro running El Capitan, on which this is the first set of macports installs, and the only copy of xemacs. </div><div><br></div><div>The problem is the same on both machines, so I assume it is not due to a version overlap, or specific to either Lion or El Capitan.</div><div><br></div><div>The problem is that when opening any file, I now get a split window, announcing a set of warnings from Autoload, of the form </div><div><div><br></div><div>(1) (warning/warning) Autoload error in: /opt/local/lib/xemacs/xemacs-packages/lisp/zenirc/auto-autoloads:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Already loaded</div></div><div><br></div><div>(and 129 more for various other files)</div><div><br></div><div>These are explained in the xemacs FAQ Q 2.5.7 at </div><div><a href="http://www.xemacs.org/Documentation/21.5/html/xemacs-faq_3.html#SEC122">http://www.xemacs.org/Documentation/21.5/html/xemacs-faq_3.html#SEC122</a></div><div>but not what to do about them.</div><div><br></div><div>If I give xemacs the command</div><div>M-x list-load-path-shadows</div><div>five load-path shadowings are reported as </div><div><br></div><div><div>/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/cedet-common/working hides /opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/semantic/working</div><div>/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/cedet-common/sformat hides /opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/semantic/sformat</div><div>/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/xemacs-base/easy-mmode hides /opt/local/lib/xemacs-21.4.22/lisp/easy-mmode</div><div>/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/build/build-report hides /opt/local/lib/xemacs-21.4.22/lisp/build-report</div><div>/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/apel/alist hides /opt/local/lib/xemacs-21.4.22/lisp/alist</div></div><div><br></div><div>Looking at each of these pairs, they are all normal files (not symlinks)</div><div><div><br></div><div>-rw-r--r-- 1 root admin 23686 Nov 27 2007 /opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/cedet-common/working.el</div><div>-rw-r--r-- 1 root admin 23767 Aug 6 2002 /opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/semantic/working.el</div></div><div><div><br></div><div>-rw-r--r-- 1 root admin 13799 Nov 27 2007 /opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/cedet-common/sformat.el</div><div>-rw-r--r-- 1 root admin 13796 Aug 12 2002 /opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/semantic/sformat.el</div></div><div><br></div><div><div>-rw-r--r-- 1 macports admin 22285 Dec 31 2008 /opt/local/lib/xemacs-21.4.22/lisp/easy-mmode.el</div><div>-rw-r--r-- 1 root admin 22480 Nov 8 2004 /opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/xemacs-base/easy-mmode.el</div></div><div><br></div><div><div>-rw-r--r-- 1 macports admin 19420 May 9 2001 /opt/local/lib/xemacs-21.4.22/lisp/build-report.el</div><div>-rw-r--r-- 1 root admin 20112 Oct 2 2009 /opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/build/build-report.el</div></div><div><br></div><div><div>-rw-r--r-- 1 macports admin 3136 Apr 13 2001 /opt/local/lib/xemacs-21.4.22/lisp/alist.el</div><div>-rw-r--r-- 1 root admin 2989 Aug 18 2009 /opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/apel/alist.el</div></div><div><br></div><div>(plus .elc versions of the above files)</div><div><br></div><div>All properties of each of these files is identical on the two installations, so I assume that this problem is created locally by this port.</div><div><br></div><div>Sorry if this is a dumb question. There must be vast numbers of users of this port, so I don't know why I haven't seen it mentioned anywhere.</div><div><br></div><div>Thanks for help,</div><div><br></div><div>Eric</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></body></html>