From: Tassilo Horn <tassilo@member.fsf.org>
To: jidanni@jidanni.org
Cc: ding@gnus.org
Subject: Re: How to make (*) text/plain the default instead of ( ) text/html ?
Date: Fri, 22 Oct 2010 12:10:20 +0200 [thread overview]
Message-ID: <87d3r27d2r.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87zku64k98.fsf@jidanni.org> (jidanni@jidanni.org's message of "Fri, 22 Oct 2010 18:03:31 +0800")
jidanni@jidanni.org writes:
> I can't take it any more. How do I get gnus to stop using this new
> default or whatever:
> 1. ( ) text/plain (*) text/html
> and make this the default?
> 1. (*) text/plain ( ) text/html
> (info "(gnus) HTML") doesn't say.
> gnus-version "Gnus v5.13".
,----[ C-h v mm-discouraged-alternatives RET ]
| mm-discouraged-alternatives is a variable defined in `mm-decode.el'.
| Its value is
| ("text/html" "text/richtext" "text/enriched")
|
| Original value was nil
|
| Documentation:
| List of MIME types that are discouraged when viewing multipart/alternative.
| Viewing agents are supposed to view the last possible part of a message,
| as that is supposed to be the richest. However, users may prefer other
| types instead, and this list says what types are most unwanted. If,
| for instance, text/html parts are very unwanted, and text/richtext are
| somewhat unwanted, then the value of this variable should be set
| to:
|
| ("text/html" "text/richtext")
|
| Adding "image/.*" might also be useful. Spammers use it as the
| prefered part of multipart/alternative messages. See also
| `gnus-buttonized-mime-types', to which adding "multipart/alternative"
| enables you to choose manually one of two types those mails include.
|
| You can customize this variable.
`----
HTH,
Tassilo
next prev parent reply other threads:[~2010-10-22 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 10:03 jidanni
2010-10-22 10:10 ` Tassilo Horn [this message]
2010-10-22 10:24 ` jidanni
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=87d3r27d2r.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.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).