From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: loading gnus creates *Group* buffer
Date: Sun, 11 Jan 2004 22:41:08 +0100 [thread overview]
Message-ID: <8765fib1u3.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <q67zncy7yri.fsf@L75001820.us.ray.com>
"Steven E. Harris" <seh@panix.com> writes:
> Just for kicks, I tried symlinking ~/.xemacs/site-packages to
> ~/usr/local/lib/xemacs/site-packages (under which my current Gnus
> build sits), but XEmacs did not find Gnus in the lisp/gnus directory
> below.
I think that link creates a directory
~/.xemacs/site-packages/gnus/lisp, but XEmacs searches for
~/.xemacs/site-packages/lisp/gnus, instead.
The ./configure arguments that Steve gave put things in the right
directory.
WIBNI there was a convenience arg --as-personal-xemacs-package that
people could use to get the right settings automatically? Then people
could just download the most recent tarball and have a working
personal installation real quick. Even if the XEmacs package is
older.
Kai
next prev parent reply other threads:[~2004-01-11 21:41 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
2004-01-11 21:41 ` Kai Grossjohann [this message]
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=8765fib1u3.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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).