From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: W3 obsolete
Date: Fri, 24 Mar 2006 06:33:50 -0500 [thread overview]
Message-ID: <vxkirq4oz4x.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: <1143188244.408476.308600@i39g2000cwa.googlegroups.com>
"Mr. Big" <andersjak@gmail.com> writes:
> requires the w3 package which I don't have installed. Searching for it
> gives me the information that it is dead (and long live w3?).
I don't know what told you that it's dead, but the situation from my
vantage point (as an XEmacs user) seems to be:
[a] w3 is in the standard package set of recent XEmacs, and
[b] I also have w3m, which may have in fact supplanted w3.
However, I don't use nnweb, so I can't speak to how much it requires
w3 specifically -vs- whether w3m substitutes.
next prev parent reply other threads:[~2006-03-24 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 8:17 Mr. Big
2006-03-24 11:33 ` Karl Kleinpaste [this message]
2006-03-26 17:11 ` Mr. Big
2006-03-26 19:03 ` William F Hammond
[not found] ` <yxdfyl4nd4k.fsf@cs1.gmu.edu>
2006-03-28 5:55 ` marco.wahl
-- strict thread matches above, loose matches on Subject: below --
2006-03-24 8:15 Mr. Big
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=vxkirq4oz4x.fsf@mesquite.charcoal.com \
--to=karl@charcoal.com \
--cc=karl+usenet@charcoal.com \
/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).