From: Miles Bader <miles@gnu.org>
To: info-gnus-english@gnu.org, ding@gnus.org
Cc: reader@newsguy.com
Subject: Re: Why won't gnus display certain messages
Date: Tue, 13 Nov 2007 10:10:43 +0900 [thread overview]
Message-ID: <87k5onc5m4.fsf@catnip.gol.com> (raw)
In-Reply-To: <mailman.3362.1194893976.18990.info-gnus-english@gnu.org> (reader@newsguy.com's message of "Mon\, 12 Nov 2007 12\:50\:00 -0600")
reader@newsguy.com writes:
> In gnus there actually is nothing displayed for body. But viewing the
> message with `C-u g' shows these mail and mime headers. I've chopped
> out or mangled some headers and all but two lines of what gnus has
> displayed for the body.
Er, is this a trick question?
You explicitly seem to have told Gnus to not display html by default,
and to always prefer text to html if a message has both alternatives:
(setq mm-automatic-display (remove "text/html" mm-automatic-display)
mm-discouraged-alternatives '("text/html" "text/richtext"))
(setq mm-text-html-renderer (quote w3m))
Your example message has an _empty_ "text" alternative, along with a
non-empty "html" alternative, and Gnus is displaying the (empty) text
alternative (because you told it to with the above settings). The other
MUA you tried displayed the (non-empty) html alternative.
The real problem of course is that the software that sent the message
screwed up big-time by including an unusable text alternative.
-miles
--
If you can't beat them, arrange to have them beaten. [George Carlin]
next parent reply other threads:[~2007-11-13 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3362.1194893976.18990.info-gnus-english@gnu.org>
2007-11-13 1:10 ` Miles Bader [this message]
2007-11-13 1:51 ` reader
2007-11-13 7:47 ` Tassilo Horn
2007-11-16 14:38 ` reader
2007-11-12 18:50 reader
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=87k5onc5m4.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=ding@gnus.org \
--cc=info-gnus-english@gnu.org \
--cc=reader@newsguy.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).