From: Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: Functional requirements for Gnus
Date: 28 Aug 1998 14:07:40 +0200 [thread overview]
Message-ID: <vafvhndjomr.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Robert Bihlmeyer's message of "28 Aug 1998 13:22:05 +0200"
>>>>> Robert Bihlmeyer <e9426626@stud2.tuwien.ac.at> writes:
> 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.
I think it would still be convenient if one had a listing of all parts
of a multipart/alternative, so that one can choose one part to one's
liking.
But a message which is multipart/alternative should by default be
displayed in a user-customizable preferred format, the above listing
of alternatives should be an option only.
kai
--
OOP: object oriented programming; OOPS: object oriented mistakes
next prev parent reply other threads:[~1998-08-28 12:07 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
1998-08-28 12:07 ` Kai Grossjohann [this message]
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=vafvhndjomr.fsf@ramses.cs.uni-dortmund.de \
--to=grossjohann@amaunet.cs.uni-dortmund.de \
--cc=ding@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).