From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: browse-url vs. w3
Date: Fri, 23 Feb 2001 09:20:37 -0800 (PST) [thread overview]
Message-ID: <200102231720.f1NHKbP07607@sighup.aventail.com> (raw)
In-Reply-To: Joe Hildebrand's message of "23 Feb 2001 00:42:32 -0700"
Joe Hildebrand <joe@cursive.net> writes:
> When w3 renders an article, (either because someone sent HTML, or
> because the group is an HTML thing like nnslashdot) URL links get
> followed by w3 when clicked on.
>
> Anyone know of a way to get browse-url to handle those widgets instead?
> It's nice of w3 to do the rendering and all, but it's not, ummm... my
> favorite browser.
Hehehe - no offense taken. :) I sent a patch to the list a long time ago
to make w3 use browse-url instead of directly calling w3-fetch, but I don't
know if I have it any more. It is probably in the list archives.
-bp
next prev parent reply other threads:[~2001-02-23 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 7:42 Joe Hildebrand
2001-02-23 10:52 ` Kai Großjohann
2001-02-23 13:10 ` Per Abrahamsen
2001-02-23 18:21 ` Kai Großjohann
2001-02-23 17:20 ` William M. Perry [this message]
2001-12-31 2:55 ` Lars Magne Ingebrigtsen
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=200102231720.f1NHKbP07607@sighup.aventail.com \
--to=wmperry@aventail.com \
--cc=ding@gnus.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).