On Wed, Sep 8, 2010 at 3:07 AM, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
Robert Pluim writes:
> The root cause of this is that passing -no-autoloads causes XEmacs
> not to pick up my package hierarchy in ~/.xemacs. If I move stuff
> to /usr/local/share/xemacs, it all works.
> Is this expected behaviour?
Not finding stuff in .xemacs is expected. The initialization options
are not orthogonal; -no-autoloads implies -no-early-packages, and
.xemacs is where early packages are found by default. This is
documented in the output of "xemacs --help" (among other places).
The thing is, my packages are in .xemacs not because they're local
site-specific things, but because I didn't want to put them in
/usr/local, so they're not really 'early-packages' in that sense.
This non-orthogonality is dubious, IMO, but all of that stuff was
in practice added as a convenience for XEmacs developers (or for the
build process), not for developers of packages. Sorry for the
I can understand why it happens, but it does screw people who have no
access to /usr/local unless they build their own XEmacs or figure out
how to point an existing one at a different package hierarchy (which I
know is possible, but I seem to have to learn how to do it all over
again about once a year :) )
Oh well, I can live with it.
XEmacs-Beta mailing list