find-paths.el and run-in-place
(moving this discussion, about how the recent change to find-paths.el has
broken run-in-place with XEmacs defaults, to the list)
I'll try that, thanks. But then it seems it will also be necessary to change
all the package installation code, that worked until last week, to work with
your new setting, or that all users who run in place will have to specify
directory paths in their init file. Also, it will be necessary to change the
directory each time the version changes. All of this is terribly unfriendly
to users. It seems like it would be easier and more straightforward for you
to change your code so that it finds the directory that the package
installation routine uses by default.
----- Original Message -----
From: "Michael Sperber [Mr. Preprocessor]"
<sperber(a)informatik.uni-tuebingen.de>
To: "Michael Harnois" <mharnois(a)cpinternet.com>
Sent: Tuesday, December 18, 2001 8:09 AM
Subject: Re: [PATCH] generalizing face settings..., GTK face fixes
>>>>> "Michael" == Michael Harnois
<mharnois(a)cpinternet.com> writes:
Michael> On Tue, 2001-12-18 at 07:28, Michael Sperber [Mr. Preprocessor]
wrote:
>> >>>>> "Michael" == Michael Harnois
<mharnois(a)cpinternet.com> writes:
>>
>> If you run XEmacs in-place, it expects the packages to be in-place as
>> well. I'm surprised XEmacs worked at all previously---this certainly
>> wasn't by any design.
Michael> I'm not certain what you mean by "by design." Ever since the
Michael> package system was instituted -- it's been several years now,
Michael> hasn't it? -- that's where XEmacs has installed the packages
Michael> by default, run-in-place or not. That certainly seems like
Michael> "design" to me, and when it suddenly stops working, that
Michael> seems like breakage.
This has nothing to do with the package system, but rather how XEmacs
determines where to find its files at startup. The code for this was
entirely written by me before the first XEmacs with an advertised
package system came out. It tries to be smart about it, and works in
many environments and ways I never envisioned. It certainly was part
of my intention that, if you run in-place, you run *everything*
in-place, and I feel qualified to say that your being able to run in
this split setup is mere accident.
You'll probably notice that, when you create an xemacs-<version>
directory alongside the vanilla xemacs one, your setup starts working
again. I would recommend simple symlinks, however.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla