From: Hrvoje Niksic <hniksic@srce.hr>
Cc: ding@gnus.org
Subject: Re: Just when I thought I had seen it all...
Date: 23 Feb 1999 16:16:12 +0100 [thread overview]
Message-ID: <874sodrw03.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: François Pinard's message of "23 Feb 1999 09:26:44 -0500"
François Pinard <pinard@iro.umontreal.ca> writes:
> MIME summary is kind of antithetic. MIME is meant by design to be as
> transparent as possible, and so, a "summary view" of MIME structure is
> just going against the very idea of MIME.
We've been through this before, and I don't particularly feel like
debating your views here. Suffice it to say that for me it would at
least be useful to have a Summary-based view of attachments, like
gnus-uu and nndoc allowed since time immemorial.
> Seriously, yes, I sometimes use `nndoc' myself. But each time I do,
> I have the feeling that something is missing in Gnus, and I go
> through `nndoc' around the limitation. The need of `nndoc' should
> slowly fade away as MIME gets better and better implemented in Gnus.
You mean the need of nndoc/MIME? Even so, the statement may be true
for *you*, as you don't want Summary-based MIME representation.
next prev parent reply other threads:[~1999-02-23 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-09 14:44 Lars Magne Ingebrigtsen
1999-02-09 17:48 ` Jack Vinson
1999-02-09 18:03 ` Lars Magne Ingebrigtsen
1999-02-10 9:18 ` Kai.Grossjohann
1999-02-10 9:33 ` Hrvoje Niksic
1999-02-23 2:58 ` François Pinard
1999-02-23 11:33 ` Hrvoje Niksic
1999-02-23 14:26 ` François Pinard
1999-02-23 14:38 ` Steinar Bang
1999-02-23 15:33 ` François Pinard
1999-02-23 18:32 ` François Pinard
1999-02-23 15:16 ` Hrvoje Niksic [this message]
1999-02-23 18:41 ` François Pinard
1999-02-24 15:47 ` Robert Bihlmeyer
1999-02-25 4:03 ` François Pinard
1999-02-11 4:11 ` 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=874sodrw03.fsf@pc-hrvoje.srce.hr \
--to=hniksic@srce.hr \
--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).