From: Jan Nieuwenhuizen <janneke@gnu.org>
Subject: text/plain vs text/html inlining
Date: 19 Dec 2001 12:39:24 +0100 [thread overview]
Message-ID: <m3wuzj1lsj.fsf@appel.lilypond.org> (raw)
Hi,
How do I get Gnus to expand inline text/plain MIME emails; but don't
hide the fact that it contains text/html parts?
In my .gnus.el, I now have:
(setq mm-inline-override-types '("text/plain" "text/richtext"
"text/html" "multipart/alternative" "application/postscript"))
but this is a bit annoying when people send MIME emails that contain
only one part, which is text/plain. In that case, I get:
(header:) Content-Type: text/plain; charset=us-ascii; format=flowed
[1. text/plain]...
and I must enter message and press 'i'. On 'broken emails' (messages
that contain html), I get to see:
(header:) Content-Type: multipart/alternative;
1. ( ) text/plain ( ) text/html
Which is fairly ok. It would be better if the text/plain were
inlined, but it's more important to see that the message also contains
html.
Otoh, if I remove "text/plain" from the mm-inline-override-types, both
messages look the same, and I don't see what's going on; Gnus hides
all traces of the text/html part when I view the message.
Greetings,
Jan.
Btw, it would be very, very nice, if gnus would have a global
setting (or new function) to disable all kinds of magic that's now
enabled by default (and any new magic that may be added); so that
it would be easy to configure it as a normal, plain text email
reader. Here's my current list:
;; I want PLAIN text mail, thankyou.
(setq mm-inline-override-types '("text/plain" "text/richtext"
"text/html" "multipart/alternative" "application/postscript"))
(setq gnus-treat-emphasize nil)
(setq gnus-treat-fill-article nil)
(setq gnus-treat-overstrike nil)
(setq gnus-treat-dumbquotes nil)
;; Hmm, what's next?
(when (equal debian-emacs-flavor 'emacs21)
(setq gnus-treat-display-smileys nil))
(setq gnus-article-wash-html nil)
(setq gnus-article-remove-cr nil)
(setq gnus-article-hide-signature nil)
;; scary?
(setq gnus-default-posting-charset 'iso-8859-1)
(add-to-list 'gnus-group-posting-charset-alist
'(message-this-is-mail iso-8859-1 (iso-8859-1)))
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
next reply other threads:[~2001-12-19 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 11:39 Jan Nieuwenhuizen [this message]
2001-12-19 11:49 ` Karl Kleinpaste
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=m3wuzj1lsj.fsf@appel.lilypond.org \
--to=janneke@gnu.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).