From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: MIME variables
Date: 05 Jul 1999 06:20:28 +0200 [thread overview]
Message-ID: <m3r9mnafsj.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "04 Jul 1999 22:06:25 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> > `mm-inline-media-tests'
> > `mm-inlines-types'
> ^
> Why this `s'? It seems inconsistent. But maybe there's a good
> reason...
Typo. Should be "d".
> > `mm-automatic-display'
> > This is a list of types that are to be displayed "automatically",
> > but only if the above variable allows it.
>
> In this sentence, you say that non-inlined parts are *never* displayed
> automatically.
Yup. Which is good, since that's the case. :-)
> > 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.
>
> Here, you say that non-inlined parts are *seldom* displayed
> automatically. Which one is right?
I've now deleted this last part. I'm not quite sure what I was
getting it here...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-07-05 4:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-04 5:21 Lars Magne Ingebrigtsen
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 [this message]
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=m3r9mnafsj.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).