From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Forward option for Mail
Date: Tue, 16 Dec 2003 10:05:34 -0500 [thread overview]
Message-ID: <a66ee2c16ddeabb1db43043d0a4714e9@plan9.bell-labs.com> (raw)
In-Reply-To: <9d4c20b77b4ced33e02bf15da127b291@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 165 bytes --]
So it does (doing this with acme mail). Guess
I should try it more often (except that I've already
made 6 mistakes chording and this is only a 4
line message).
[-- Attachment #2: Type: message/rfc822, Size: 1957 bytes --]
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Forward option for Mail
Date: Tue, 16 Dec 2003 09:36:09 -0500
Message-ID: <9d4c20b77b4ced33e02bf15da127b291@plan9.bell-labs.com>
Elm and Mutt use "bounce" and it's a very nifty feature. But
forwarding then is a case of Mime-enclosing (or otherwise isolating)
the original message in a bigger scope where the forwarder can add
her comments.
Nedmail already does all this. You just lose it
with the acme interface.
next prev parent reply other threads:[~2003-12-16 15:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 14:36 David Presotto
2003-12-16 14:15 ` Russ Cox
2003-12-16 15:05 ` David Presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-15 8:47 Skip Tavakkolian
2003-12-15 9:04 ` rob pike, esq.
2003-12-15 10:17 ` Skip Tavakkolian
2003-12-15 16:53 ` Rob Pike
2003-12-15 10:28 ` Skip Tavakkolian
2003-12-16 1:27 ` Russ Cox
2003-12-16 1:53 ` Jim Choate
2003-12-16 1:52 ` Russ Cox
2003-12-16 2:56 ` Jim Choate
2003-12-16 7:26 ` Skip Tavakkolian
2003-12-16 13:38 ` Jim Choate
2003-12-16 13:47 ` Axel Belinfante
2003-12-16 14:16 ` Lucio De Re
2003-12-16 14:12 ` Russ Cox
2003-12-17 2:10 ` Charles Forsyth
2003-12-17 11:16 ` David Lukes
2003-12-17 6:06 ` Skip Tavakkolian
2003-12-17 5:14 ` andrey mirtchovski
2003-12-17 6:41 ` Skip Tavakkolian
2003-12-17 8:20 ` andrey mirtchovski
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=a66ee2c16ddeabb1db43043d0a4714e9@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).