From: reader@newsguy.com
To: info-gnus-english@gnu.org
Cc: ding@gnus.org
Subject: Re: Why won't gnus display certain messages
Date: Mon, 12 Nov 2007 19:51:51 -0600 [thread overview]
Message-ID: <873avax5tb.fsf@newsguy.com> (raw)
In-Reply-To: <87k5onc5m4.fsf@catnip.gol.com>
Miles Bader <miles@gnu.org> writes:
> 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:
Hehe... yes, a poorly phrased question. I should have asked why
nothing was displayed. In all cases thus far gnus has presented me
with the text and a mime part to allow me to have the html rendered if
so desired by 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.
But I wasn't presented with the Mime part to have rendered if so
desired as in all cases up to now.
Is there something more about the message that is causing that to happen?
Or some other formulation for .gnus that would have caused something
to be displayed?
next prev parent reply other threads:[~2007-11-13 1:51 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
2007-11-13 1:51 ` reader [this message]
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=873avax5tb.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=ding@gnus.org \
--cc=info-gnus-english@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).