From: Simon Josefsson <jas@extundo.com>
Cc: Simon Josefsson <jas@extundo.com>, ding@gnus.org
Subject: Re: Gnus displaying MIME automatically
Date: Mon, 26 Nov 2001 20:00:58 +0100 [thread overview]
Message-ID: <ilu667xicgl.wl@dhcp128.extundo.com> (raw)
In-Reply-To: <874rnhe54b.fsf@yahoo.com>
At Mon, 26 Nov 2001 19:53:08 +0100,
Alex Schroeder wrote:
>
> Yes, I thought so, too. So much the worse, haha. But I am not sure
> which part actually started the xterm window -- perhaps you are right
> and it was the text/html part, not the audio/x-wav part which (I hope)
> would have been a button.
You quoted the *Message* buffer starting w3m, so I guess it would be
the text/html part.
> Does it seem plausible then that I got a mail with no text/plain and
> only text/html in it -- thus the HTML is displayed.
Yes.
> And the reason is that text/html is a discouraged alternative -- but
> if it is the only alternative, it will be used. Correct?
Yes.
> The correct solution would be to remove text/html from
> mm-automatic-display.
Yup.
> Then I don't have to specify text/html as a discouraged alternative
> anymore -- or do I?
Well, they are orthogonal, so you must decide. The first controls if
text/html should be displayed automatically, and the latter which part
of a multipart/altnerative to chose.
> Or would it make more sense to add text/html to
> gnus-buttonized-mime-types?
I don't think so, this variable only control if you get a button or
not. It doesn't do anything about automaically inlining the part or
not.
> Anyway, is there any other place but the "MIME Commands" node in the
> Gnus manual where such things are explained?
The Emacs MIME manual.
next prev parent reply other threads:[~2001-11-26 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y9ku1ld2.fsf@yahoo.com>
2001-11-26 15:20 ` Simon Josefsson
2001-11-26 18:53 ` Alex Schroeder
2001-11-26 19:00 ` Simon Josefsson [this message]
2001-11-26 21:07 ` Alex Schroeder
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=ilu667xicgl.wl@dhcp128.extundo.com \
--to=jas@extundo.com \
--cc=ding@gnus.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).