From: Jesse Rosenthal <jrosenthal@jhu.edu>
To: David Bremner <david@tethera.net>,
Jameson Graef Rollins <jrollins@finestructure.net>,
Carl Worth <cworth@cworth.org>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] Restore original keybinding ('r' = reply-to-all)
Date: Thu, 28 Jun 2012 11:24:21 -0400 [thread overview]
Message-ID: <87ehozmpcq.fsf@jhu.edu> (raw)
In-Reply-To: <87hatwqoz9.fsf@maritornes.cs.unb.ca>
On Wed, 27 Jun 2012, David Bremner <david@tethera.net> wrote:
> My bias is probably apparent in that I pushed the original patch...
And mine in that the first thing I did in my .emacs, back in 2009 or so,
was write a reply-to-sender function, and reverse the behavior. In fact,
I just got around to using the built-in behavior in the last couple of
weeks or so.
> I think the there is potential for unfortunate mistakes with either set
> of bindings. On the one hand sending replies to unintended people can be
> very embarrassing.
Or something close to career-threatening. If you are in an office
situation with non-technical folks, which I am, and which more and more
of our users will likely be, replying-all accidentally can be quite
dire. The deans and the chair of my department frequently send out
requests for votes or comments to the whole department or faculty. In
many cases, the information requested is ridiculously confidential for
the medium; an accidental reply-all would be -- and I'm not overstating
-- disastrous. Incidences of this are rare, because it's not the default
in most standard clients. Even those coming from mutt or gnus are likely
to be surprised.
If it's not obvious, I'm pretty strongly against Carl's roll-back. I
could, of course, just uncomment my old correction in my .emacs, but I
think it's a change that could hurt users. Those who are more likely to
prefer the reply-all behavior are more likely to be able to change the
defaults. Those who aren't likely to change the defaults are more likely
to be bitten, badly, by a default reply-all behavior.
> On the other hand, forgetting to reply to the group can also be
> problematic.
True that. My solution to this has been to write what I call a
"smart-reply" function -- it replies-all when you want it to, and
replies-to-sender the rest of the time. It's pretty simple, and I sent
it into the list before[0], but the basic functionality is that I give
it a list of to: addresses that I will want to reply-all to by default
(essentially, my mailing lists), and those will, by default, reply
all. Others will by default be reply-to-sender. I realize this
complicates the setup a bit, but it makes everyday use quite easy.
Best,
Jesse
[0] id:"87hay8xdoe.fsf@jhu.edu"
next prev parent reply other threads:[~2012-06-28 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 16:46 [PATCH] Restore original keybinding ('r' = reply-to-all) Carl Worth
2012-06-27 17:55 ` Jameson Graef Rollins
2012-06-27 18:32 ` Daniel Schoepe
2012-06-28 0:06 ` David Bremner
2012-06-28 7:02 ` Mark Walters
2012-06-28 16:16 ` Jameson Graef Rollins
2012-06-28 8:28 ` Jani Nikula
2012-06-28 15:24 ` Jesse Rosenthal [this message]
2012-06-28 16:05 ` Philip Hands
2012-06-28 16:21 ` Jameson Graef Rollins
2012-06-28 17:01 ` Thomas Jost
2012-06-28 17:59 ` Carl Worth
2012-06-29 19:05 ` [UGLY DFAFT PATCH] draft: emacs: custom variable to choose default reply-to behaviour Tomi Ollila
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehozmpcq.fsf@jhu.edu \
--to=jrosenthal@jhu.edu \
--cc=cworth@cworth.org \
--cc=david@tethera.net \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).