From: Hrvoje Niksic <hniksic@iskon.hr>
Subject: Re: Responding to a MIME attachment
Date: 01 Dec 1999 14:42:49 +0100 [thread overview]
Message-ID: <9t9u2m2bwva.fsf@mraz.iskon.hr> (raw)
In-Reply-To: Shenghuo ZHU's message of "01 Dec 1999 08:36:20 -0500"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> I guess the message is not message/rfc822 attachment but old format
> forward and the part is generated by mm-uu. To verify my conjecture,
> type (C-u g).
Yes, that's the case. The problem with the mm-uu stuff is that it
makes things _look_ as if you know what's going on, except you don't,
and things fail mysteriously.
> I think we need a reply function on a mm part.
That might be a bit of a clutter, because you'd then also need a
wide-reply function, a send-forward function, an include-into-digest
function, etc. What we need is a way to insert the part into a
summary, so you can do with it whatever you'd normally do with summary
buffers.
One more reason why C-d should use the mm stuff. :-)
next prev parent reply other threads:[~1999-12-01 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-01 11:18 Hrvoje Niksic
1999-12-01 13:36 ` Shenghuo ZHU
1999-12-01 13:42 ` Hrvoje Niksic [this message]
1999-12-01 22:37 ` Lars Magne Ingebrigtsen
1999-12-02 9:09 ` Hrvoje Niksic
2000-04-21 23:59 ` 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=9t9u2m2bwva.fsf@mraz.iskon.hr \
--to=hniksic@iskon.hr \
/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).