From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: MIME variables
Date: 04 Jul 1999 07:21:16 +0200 [thread overview]
Message-ID: <m3k8shhtwz.fsf@quimbies.gnus.org> (raw)
I think the following should reflect the state in 0.91:
Customization
=============
`mm-inline-media-tests'
This is an alist where the key is a MIME type, the second element
is a function to display the part "inline" (i.e., inside Emacs),
and the third element is a form to be `eval'ed to say whether the
part can be displayed inline.
This variable specifies whether a part _can_ be displayed inline,
and, if so, how to do it. It does not say whether parts are
_actually_ displayed inline.
`mm-inlines-types'
This, on the other hand, says what types are to be displayed
inline, if they satisfy the conditions set by the variable above.
It's a list of MIME media types.
`mm-automatic-display'
This is a list of types that are to be displayed "automatically",
but only if the above variable allows it. That is, only inlinable
parts are usually displayed automatically, but in the end, this is
up to the display agent that's using the MIME library.
`mm-attachment-override-types'
Some MIME agents create parts that have a content-disposition of
`attachment'. This variable allows overriding that disposition and
displaying the part inline.
`mm-discouraged-alternatives'
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/richtech' parts are
somewhat unwanted, then the value of this variable should be set
to:
("text/html" "text/richtext")
`mm-all-images-fit'
If non-`nil', all images will be deemed to fit into the buffer,
even when they don't.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next reply other threads:[~1999-07-04 5:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-04 5:21 Lars Magne Ingebrigtsen [this message]
1999-07-04 15:55 ` Hrvoje Niksic
1999-07-04 20:09 ` Kai.Grossjohann
1999-07-05 4:17 ` Lars Magne Ingebrigtsen
1999-07-05 4:16 ` Lars Magne Ingebrigtsen
1999-07-05 13:15 ` Hrvoje Niksic
1999-07-05 13:52 ` Lars Magne Ingebrigtsen
1999-07-05 13:54 ` Hrvoje Niksic
1999-07-06 4:42 ` Lars Magne Ingebrigtsen
1999-07-06 15:17 ` Hrvoje Niksic
1999-07-06 16:01 ` Lars Magne Ingebrigtsen
1999-07-06 21:41 ` David Kågedal
1999-07-07 11:53 ` Robert Bihlmeyer
1999-07-08 7:11 ` Lars Magne Ingebrigtsen
1999-07-04 20:06 ` Kai.Grossjohann
1999-07-05 4:20 ` Lars Magne Ingebrigtsen
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=m3k8shhtwz.fsf@quimbies.gnus.org \
--to=larsi@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).