From: Steve Youngs <sryoungs@bigpond.net.au>
Subject: Re: loading gnus creates *Group* buffer
Date: Fri, 09 Jan 2004 12:39:58 +1000 [thread overview]
Message-ID: <microsoft-free.87eku9g801.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <q67zncy7yri.fsf@L75001820.us.ray.com> (Steven E. Harris's message of "Thu, 08 Jan 2004 16:26:41 -0800")
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
|--==> "SEH" == Steven E Harris <seh@panix.com> writes:
SEH> So a home-built Gnus will not overwrite or take up residence in
SEH> the same place as a would-be real Gnus package?
When the home-built Gnus was configured with default settings and the
"would-be real Gnus package" is that which is distributed by
XEmacs.org, then yes, that is correct.
SEH> Would the real Gnus package wind up in
SEH> <emacs-roots>/lib/xemacs/xemacs-packages?
Providing it is the one distributed by XEmacs.org, yes.
The _only_ packages that should be in (xemacs|mule)-packages/ are the
"official" packages that are distributed by XEmacs.org. The
site-packages/ directories are for other packages. That's why the
Gnus from Gnus.org defaults to installing into site-packages/.
SEH> Just for kicks, I tried symlinking ~/.xemacs/site-packages to
SEH> ~/usr/local/lib/xemacs/site-packages (under which my current
SEH> Gnus build sits), but XEmacs did not find Gnus in the lisp/gnus
SEH> directory below.
OK, that's weird. That should have worked. I'll have to test that.
I'll get back to you on that.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Ashes to ashes, dust to dust. |
| The proof of the pudding, is under the crust. |
|------------------------------<sryoungs@bigpond.net.au>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-01-09 2:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 3:07 Katsumi Yamaoka
2004-01-07 3:10 ` Lars Magne Ingebrigtsen
2004-01-07 3:14 ` Katsumi Yamaoka
2004-01-07 16:10 ` Steven E. Harris
2004-01-07 19:52 ` Steve Youngs
2004-01-07 21:17 ` Steven E. Harris
2004-01-07 23:24 ` Steve Youngs
2004-01-08 1:56 ` Istvan Marko
2004-01-08 23:11 ` Steven E. Harris
2004-01-08 23:57 ` Steve Youngs
2004-01-09 0:26 ` Steven E. Harris
2004-01-09 2:39 ` Steve Youngs [this message]
2004-01-11 21:41 ` Kai Grossjohann
2004-01-11 22:59 ` Steve Youngs
2004-01-11 23:17 ` Steven E. Harris
2004-01-12 0:00 ` Steve Youngs
2004-01-12 1:33 ` Steven E. Harris
2004-01-12 4:21 ` Steve Youngs
2004-01-12 17:40 ` Steven E. Harris
2004-01-12 22:25 ` Steve Youngs
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=microsoft-free.87eku9g801.fsf@eicq.dnsalias.org \
--to=sryoungs@bigpond.net.au \
/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).