From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: Compiling No Gnus for XEmacs
Date: Wed, 08 Sep 2010 13:28:33 +0200 [thread overview]
Message-ID: <pknmxrsh3tp.fsf@gmail.com> (raw)
In-Reply-To: <b4mhbi0n89f.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Robert Pluim wrote:
>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> [...]
>>> I'm unable to reproduce that. It seems to work for me...
>
>> On further investigation, I now see why this happens. I bet you have
>> your packages installed in /usr/local/share/xemacs, right? I have mine
>> under ~/.xemacs, putting them in /usr/local solves it.
>
> But why does it do the trick?
> Because of the -no-autoloads option, XEmacs doesn't know the module
> from which to get `defadvice'. For it dgnushack.el provides the
> autoload:
>
> (unless (fboundp 'defadvice)
> (autoload 'defadvice "advice" nil nil 'macro))
>
> Even with that if XEmacs fails in loading advice.elc, it will mean
> there's no such module in the `load-path' directories. I got
> (in Windows Vista):
>
> $ xemacs -batch -no-autoloads -eval '(message "%s" (locate-library "advice"))'
> /usr/share/xemacs/xemacs-packages/lisp/xemacs-base/advice.elc
>
> I can hardly imagine why the behavior changes by changing the
> installation directory.
It's because of the way XEmacs has early- and non-early package
paths. ~/.xemacs is where the early packages are searched for, and
-no-autoloads suppresses looking there, but does not suppress looking in
the other package paths, hence moving the files to /usr/local/ makes
things work again.
Robert
next prev parent reply other threads:[~2010-09-08 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 17:09 Robert Pluim
2010-09-07 17:14 ` Lars Magne Ingebrigtsen
2010-09-07 17:43 ` Robert Pluim
2010-09-08 4:56 ` Katsumi Yamaoka
2010-09-08 11:28 ` Robert Pluim [this message]
2010-09-08 23:42 ` Katsumi Yamaoka
2010-09-08 3:47 ` Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pknmxrsh3tp.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).