Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Cc: Andy Piper the Xemacs-Win Master <andyp@bea.com>,
	Xemacs on MS Windows Discussion List <xemacs-winnt@xemacs.org>,
	"Xemacs General @org.Xemacs Discussion List" <xemacs@xemacs.org>,
	GNUS Newsreader <ding@gnus.org>,
	Emacs/W3 Betatest MailList <w3-beta@cs.indiana.edu>
Subject: Re: Installing GNUs and W3 on Xemacs--i686-pc-Cygwin--21.1.13 -- HELP
Date: Fri, 2 Mar 2001 19:07:54 -0500	[thread overview]
Message-ID: <86vgprq2qf.fsf@totally-fudged-out-message-id> (raw)
In-Reply-To: "David A. Cobb"'s message of "Thu, 01 Mar 2001 12:35:46 -0500"

"David A. Cobb" <superbiskit@home.com> writes:

> [A thousand pardons for the massive cross-post, I'm getting nowhere fast
> 
> with this.  Flame if you must]
> 
> I originally installed the Xemacs-21.1.13 packages as posted at
> xemacs.org.
> Since this installation I have never successfully used W3; it gets as
> far as a
> message from /advise/ about "cannot locate documentation file
> /usr/local/lib-src/DOC."
> 
> Having found no help for that symptom, I thought of re-installing W3,
> selecting the 4.0beta version from xemacs.org/pub/xemacs/emacs-w3.
> Reading the configure --help, I see it wishes to know where to find
> Gnus.  So for practice I downloaded the latest Gnus to build it first -
> then I'd know where it is :-}.

Does removing the gunk in w3-xemac.el calling defadvice help at all?

-bp



      parent reply	other threads:[~2001-03-03  0:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01 17:35 David A. Cobb
2001-03-01 17:50 ` Andy Piper
2001-03-01 22:10   ` Installing GNUs and W3 on Xemacs--i686-pc-Cygwin--21.1.13-- HELP David A. Cobb
2001-03-03  0:07 ` William M. Perry [this message]

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=86vgprq2qf.fsf@totally-fudged-out-message-id \
    --to=wmperry@aventail.com \
    --cc=andyp@bea.com \
    --cc=ding@gnus.org \
    --cc=w3-beta@cs.indiana.edu \
    --cc=xemacs-winnt@xemacs.org \
    --cc=xemacs@xemacs.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).