From: david.goldberg6@verizon.net (David S. Goldberg)
Subject: Re: Allow people to circumvent W3 for HTML
Date: Fri, 19 Oct 2001 12:24:22 -0400 [thread overview]
Message-ID: <m1bitdbk37t.fsf@blackbird.mitre.org> (raw)
In-Reply-To: <adynaaql.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Fri, 19 Oct 2001 17:52:02 +0200")
How I deal with text/html email:
(setq mm-discouraged-alternatives (list "multipart/related"
"text/html" "text/richtext"))
(setq mm-automatic-external-display '("text/html"))
(setq mm-inline-override-types '("text/html"))
This results in all text/html showing up as a button. I then do a
view-interactive if I actually want to read it. I specify a shell
script that calls netscape with the -remote option to pop up a new
window as the viewer. I purposely do not pass the part to netscape
automatically. 99% of the text/html I get I don't actually want to
see. Unfortunately a lot of people at work send messages that contain
both text/plain and text/html but send it as multipart/mixed instead
of multipart/alternative so the text/html is just a redundant
attachment.
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2001-10-19 16:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 13:39 Kai Großjohann
2001-10-19 14:19 ` Oystein Viggen
2001-10-19 15:52 ` Frank Schmitt
2001-10-19 16:24 ` David S. Goldberg [this message]
2001-10-19 17:54 ` Kai Großjohann
2001-10-19 18:09 ` David S. Goldberg
2001-10-19 21:27 ` Kai Großjohann
2001-10-20 10:11 ` Per Abrahamsen
2001-10-20 18:30 ` Henrik Enberg
2001-10-21 8:20 ` Per Abrahamsen
2001-10-21 14:25 ` Lloyd Zusman
2001-10-19 16:30 ` Kai Großjohann
2001-10-21 12:06 ` Oystein Viggen
2001-10-20 6:01 ` Daniel Pittman
2001-10-20 9:39 ` Simon Josefsson
2001-10-20 10:55 ` Kai Großjohann
2001-10-20 11:25 ` Simon Josefsson
2001-10-20 11:47 ` Daniel Pittman
2001-10-20 12:00 ` Simon Josefsson
2001-10-20 18:08 ` Kai Großjohann
2001-10-21 1:41 ` Daniel Pittman
2001-10-21 8:35 ` 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=m1bitdbk37t.fsf@blackbird.mitre.org \
--to=david.goldberg6@verizon.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).