From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: `b'
Date: 18 Nov 1998 19:43:07 -0500 [thread overview]
Message-ID: <oqu2zw1pic.fsf@icule.progiciels-bpi.ca> (raw)
In-Reply-To: Hrvoje Niksic's message of "30 Oct 1998 04:05:57 +0100"
Hrvoje Niksic <hniksic@srce.hr> écrit:
> > > C-d is not well-designed in comparison to other MIME viewers out
> > > there. I've written about this before.
> Also, C-d is already too overloaded -- it attempts to do all kinds of
> things with the messages. Adding tree-like MIME display looks like
> one too much to me.
Is that really an argument? If `C-d' does not have a meaning for MIME
messages, I see no problem that it gets one. The `nndoc' concept, per
definition, should be able to do many intelligent things, not only one.
> In a true MIME-viewing mode, `o' should save only the message body, one
> should be able to access the unhacked headers, uuencoded messages should
> work just like they do with regular buttons, etc. [...] I'd like for
> instance `o' to save the messages without the (bogus) headers. I would
> also prefer headers not to be inherited and shown.
`C-d' does not attempt to trigger a MIME-viewing mode. It only generates
full, complete, valid messages representing useful subtrees of the MIME tree
for a single original message. You then use any command able to manoeuvre
_full_ messages on subtrees. Here, `o' does not get specially overloaded,
and has no reason to be. It means what it always meant for full messages.
If you imply that `C-d' is meant for other things it was really meant for,
then of course, it is likely that it was not well designed to do them.
> For the latter, I'd like the code to use the existing Gnus MIME engine
> (the mm-* stuff), so that it works for uuencoded files, etc.
I think, I may be biased (:-), that `C-d' does its job well, and even, that
the code is not so badly written. Maybe it could do better now using `mm-*'
stuff? Such `mm-*' did not exist at the time `C-d' became able to split
MIME parts, and `C-d' has most probably not been reevaluated since then.
You say that using `mm-*' will give us `uuencoded' parts? Anything else?
--
François Pinard mailto:pinard@iro.umontreal.ca
Join the free Translation Project! http://www.iro.umontreal.ca/~pinard
next prev parent reply other threads:[~1998-11-19 0:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-13 0:53 `b' Lars Magne Ingebrigtsen
1998-10-13 2:04 ` `b' Jason R Mastaler
1998-10-13 15:30 ` `b' Simon Josefsson
1998-10-13 16:39 ` `b' Kai Grossjohann
1998-10-13 17:08 ` `b' Simon Josefsson
1998-10-14 8:23 ` `b' Lee Willis
1998-10-14 9:57 ` `b' Kai Grossjohann
1998-10-14 10:33 ` `b' Hrvoje Niksic
1998-10-30 3:00 ` `b' François Pinard
1998-10-30 3:05 ` `b' Hrvoje Niksic
1998-11-01 0:22 ` `b' Kai Grossjohann
1998-11-01 0:54 ` `b' Hrvoje Niksic
1998-11-01 13:03 ` `b' Kai Grossjohann
1998-11-01 20:59 ` `b' Hrvoje Niksic
1998-11-07 14:05 ` `b' Lars Magne Ingebrigtsen
1998-11-19 0:43 ` François Pinard [this message]
1998-11-19 6:00 ` `b' Lars Magne Ingebrigtsen
1998-11-19 11:32 ` `b' Hrvoje Niksic
1998-11-19 11:11 ` `b' Hrvoje Niksic
1998-10-14 14:01 ` `b' Simon Josefsson
1998-10-14 20:51 ` `b' Kai Grossjohann
1998-10-15 12:47 ` `b' Simon Josefsson
1998-10-17 20:27 ` `b' Lars Magne Ingebrigtsen
1998-10-17 20:29 ` `b' Lars Magne Ingebrigtsen
1998-10-17 20:25 ` `b' 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=oqu2zw1pic.fsf@icule.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--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).