From: Robert Bihlmeyer <e9426626@stud2.tuwien.ac.at>
Subject: Re: Functional requirements for Gnus
Date: 28 Aug 1998 13:22:05 +0200 [thread overview]
Message-ID: <lfyas9bbc2.fsf@mars.zserv.tuwien.ac.at> (raw)
In-Reply-To: Kai Grossjohann's message of "28 Aug 1998 11:29:47 +0200"
>>>>> On 28 Aug 1998 11:29:47 +0200
>>>>> Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de> said:
Kai> I find that there are at least three different ways of
Kai> presenting MIME messages to the user (especially multipart
Kai> messages).
You seem to be mainly concerned with multipart/mixed. What about
multipart/alternative? m/digest, m/parallel, m/related should probably
be treated much like m/mixed. There are also multipart/signed,
multipart/encrypted, which should be handed over to mailcrypt.
Kai> (1) `The TM alternative'
Kai> [...] Textual parts also have the text included below the
Kai> button. [...]
This can extend to graphical parts at least in XEmacs. Hell, videos
even.
Kai> (2) `The digest alternative'
Autoexplosion should be possible, like the following:
Kai> But how should the original article be displayed? One
Kai> possibility would be to split the article window into two
Kai> parts, one showing the nndoc digest summary and the other
Kai> showing the message part currently selected.
[...]
Kai> Another possibility would be to
Kai> concatenate the textual parts, maybe interspersed with
Kai> little markers showing where the non-textual MIME parts are.
The latter is like (1) really, isn't it.
Kai> (3) `The X u alternative'
I think this is like (2), only with the submessages in the summary
buffer, rather than a separate buffer.
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:[~1998-08-28 11:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-26 14:15 Steinar Bang
1998-08-26 15:22 ` Simon Josefsson
1998-08-26 15:29 ` Jean-Yves Perrier
1998-08-26 16:05 ` Simon Josefsson
1998-08-26 17:21 ` William M. Perry
1998-08-27 9:28 ` Steinar Bang
1998-08-28 9:29 ` Kai Grossjohann
1998-08-28 10:15 ` David Hedbor
1998-08-28 11:22 ` Robert Bihlmeyer [this message]
1998-08-28 12:07 ` Kai Grossjohann
1998-08-28 14:37 ` François Pinard
1998-08-28 15:05 ` Kai Grossjohann
1998-08-28 16:04 ` François Pinard
1998-08-28 16:26 ` Kai Grossjohann
1998-08-29 11:18 ` Lars Magne Ingebrigtsen
1998-08-31 13:03 ` Kai Grossjohann
1998-08-31 14:01 ` François Pinard
1998-08-28 16:29 ` Kai Grossjohann
1998-08-28 16:13 ` Phil Humpherys
1998-08-31 8:49 ` Steinar Bang
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=lfyas9bbc2.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).