From: "Kai Großjohann" <Kai.Grossjohann@CS.Uni-Dortmund.DE>
Subject: W3 installation and Gnus?
Date: 19 Jul 1999 23:36:09 +0200 [thread overview]
Message-ID: <vafyagccofq.fsf@petty.cs.uni-dortmund.de> (raw)
Now that Emacs 20.4 is out, I'm taking the time to rebuild my
site-lisp directory from scratch. Right now, I'm installing
w3-4.0pre44, and the configure script tells me that it's checking for
a recent Gnus version (it seems to be checking for mm-decode or
something) and tells me no.
But I'm pretty sure that pgnus-0.95 is fairly recent :-)
So, how do I tell the W3 configure script that I've got pgnus-0.95
installed? (There is a directory site-lisp/pgnus-0.95 which contains
the *.el and *.elc files, and subdirs.el tells me it's adding this
directory to load-path, right?)
But the configure script calls "emacs -batch" which inhibits the
site-lisp stuff, I think.
So, what to do?
kai
--
Life is hard and then you die.
next reply other threads:[~1999-07-19 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-19 21:36 Kai Großjohann [this message]
1999-07-19 21:46 ` Peter von der Ahé
1999-07-19 22:14 ` Kai Großjohann
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=vafyagccofq.fsf@petty.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).