From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] bounce feature
Date: Tue, 24 Mar 2009 19:37:16 -0700 [thread overview]
Message-ID: <1237948579-sup-3742@entry> (raw)
In-Reply-To: <1237938120-sup-2351@tangerine.lanl.gov>
Reformatted excerpts from John Bent's message of 2009-03-24:
> Some of the recent emails got me remembering the only thing I miss
> about pine: bounce. It was like forward but for the base case when
> you didn't want to edit the message at all. Forward works OK, but
> it's about 4-5 extra keystrokes.
Not quite the same as bounce, but D in thread-view-mode will edit the
message as a new one. Bounce preserves the original sender, and this one
rewrites it, but if anything this is more like forward than bounce is.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-03-25 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 23:43 John Bent
2009-03-25 2:37 ` William Morgan [this message]
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=1237948579-sup-3742@entry \
--to=wmorgan-sup@masanjin.net \
/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