OK, what the heck is an EMACSPACKAGEPATH key doing in my registry? And why
does (getenv "EMACSPACKAGEPATH") return its value. <sigh> I knew running
windows was going to be painful again.
Anyway, if I comment out the code in
packages.el:packages-find-all-package-hierarchies that parses the
EMACSPACKAGEPATH env var, then configure-package-path is used and it is
parsed correctly (this is in vanilla beta, without Vin's patch), and all the
packages are found.
I'm going to try again with Vin's patch in a second.
Robert
On 3/9/06, Robert Pluim <rpluim(a)gmail.com> wrote:
On 3/8/06, Michael Sperber <sperber(a)informatik.uni-tuebingen.de> wrote:
>
>
> > configure-package-path: ("~\\.xemacs" "" "c:\\Program
> > Files\\XEmacs\\site-packag
> > es" "c:\\Program Files\\XEmacs\\xemacs-packages")
>
> Are you really using an up-to-date version here? The semantics of
> `configure-package-path' changed recently, back to the 21.4 version.
> But you really should have this unset.
With Vin's patch it's set by nt/xemacs.mak if PACKAGE_PREFIX is set, which
it is in this case (in nt/config.inc). Unsetting it has no effect.
What is the new way of telling emacs where the packages are?
Robert
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla