From: Robert Bihlmeyer <e9426626@stud2.tuwien.ac.at>
Subject: Re: Bug in multipart/alternative
Date: 20 Apr 1999 15:28:23 +0200 [thread overview]
Message-ID: <lf1zhfzaiw.fsf@mars.zserv.tuwien.ac.at> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "18 Apr 1999 20:05:14 +0200"
Hi,
>>>>> On 18 Apr 1999 20:05:14 +0200
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> said:
>> > What on earth should one do? Should there be a test for
>> > multipart/* to see whether (after iterating over the arbitrarily
>> > complex tree) Gnus really can display it after all?
[...]
Lars> Yes, but I'm having difficulty envisioning the predicate
Lars> function here. What are the rules we are after, really?
A part is displayable, if
a) it is a non-aggregate (text/*, image/*, ...), and the usual tests
succeed (can this Emacs display html, gif, etc.)
b) it is a multipart/alternative, and one of its subpart is
displayable
c) is is a multipart/*, and all its subparts are displayable
b+c do the recursion thingy.
Robbe
--
Robert Bihlmeyer reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at> <http://stud2.tuwien.ac.at/~e9426626/sig.html>
next prev parent reply other threads:[~1999-04-20 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87hfsp969d.fsf@mattdav.vip.best.com>
1999-04-18 11:05 ` Lars Magne Ingebrigtsen
1999-04-18 11:49 ` Bruce Stephens
1999-04-18 18:05 ` Lars Magne Ingebrigtsen
1999-04-18 18:37 ` Bruce Stephens
1999-04-20 13:28 ` Robert Bihlmeyer [this message]
1999-06-12 2:22 ` Lars Magne Ingebrigtsen
1999-04-18 18:38 ` Peter von der Ahé
1999-04-18 19:33 ` Hrvoje Niksic
1999-04-20 4:31 ` François Pinard
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=lf1zhfzaiw.fsf@mars.zserv.tuwien.ac.at \
--to=e9426626@stud2.tuwien.ac.at \
/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).