Mats Lidell <matsl(a)xemacs.org> writes:
>>>>> Michael Sperber <sperber(a)deinprogramm.de>
> 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?
It could be done. My point is that, at least once upon a time, there
were people who didn't do it to be the way you want it to be. They do
have a point in that the already complicated behavior gets more
complicated when it's different at dump time.
XEmacs-Beta mailing list