>>>> Michael Sperber <sperber(a)deinprogramm.de>
writes:
It is intentional, to some degree: A long time ago, people screamed
bloody murder at me when the startup paths didn't give configure'd
paths precedence over those determined at run time. startup.el is just
the first file that knows about those paths. So there's no good
solution here that will make everybody happy, I'm afraid.
But this happens while building the dump. What ever happens when you
start your xemacs is another thing I think. Couldn't this behavior be
controlled some how so that when building the dump we don't do this?
I'm not sure why we actually have the elc-files that we dump with
xemacs also available in the load-path. I understand that it might be
convenient in a lot of ways but since they are dumped they should
never have to be loaded again.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta