From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: avoiding w3 following embedded URLs
Date: Wed, 26 Feb 2003 18:43:29 +0100 [thread overview]
Message-ID: <un0kjgcou.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <hearnmtt.fsf@random.localnet.unwireduniverse.com>
Derrell.Lipman@UnwiredUniverse.com writes:
> How do I tell w3 not to follow embedded URLs in a received HTML message? Most
> of the time, I avoid HTML completely by preferring the text/plain alternative
> when it is available. When it isn't, though, I'd like to just display whatever
> HTML there is in the message itself without any URLs being followed.
> "M-x apropos w3" didn't show anything that seemed encouraging...
How about using a w3m (the best for this purpose IMO), links or lynx
for this purpose? As you use Oort, you can say something like
(setq mm-text-html-renderer 'w3m)
in .gnus (at least with recent Oorts, you might have to update)
--
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.
prev parent reply other threads:[~2003-02-26 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 14:22 Derrell.Lipman
2003-02-26 17:43 ` Frank Schmitt [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=un0kjgcou.fsf@hschmi22.userfqdn.rz-online.de \
--to=usereplyto@frank-schmitt.net \
--cc=replies@Frank-Schmitt.net \
/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).