From: Richard M Stallman <rms@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: Change in rmail-reply
Date: Fri, 30 Jan 2009 02:25:46 -0500 [thread overview]
Message-ID: <E1LSnl4-0002AP-C4@fencepost.gnu.org> (raw)
In-Reply-To: <874ozidq89.fsf@xemacs.org> (stephen@xemacs.org)
> The RFC is clear, but it seems to be clearly wrong. If John Doe sends
> a message to you, and you resend it to me, and I do "reply to all", it
> seems clear that my reply should by default go to [you]
If the resender wishes to indicate interest in the conversation, they
can do this in a number of ways, including adding themselves as a CC,
specifying a Reply-To header, or forwarding the message (ie,
encapsulating the original text in a new message with themselves in
the From header).
I realize now that the resender is not a real issue. He is most
likely one of the recipients of the original message, or reached via
them, so sending a response there will reach him.
The real issue is the other people to whom the message was resent.
If he resends the message to rms@gnu.org and stephen@xemacs.org,
and I reply, shouldn't my reply go to you?
Adding the other recipients to the CC list may be difficult. With
rmail-resend, the user does not edit the message. The idea is that
all he needs to do is specify where to resend to, in the minibuffer,
and then it goes there. Isn't that what resending is for?
As for fowarding, that is no substitute, since the new header does not
include the sender or other recipients of the original message. When
you want to exclude them, forwarding is suitable. Otherwise, it isn't.
If resending as a feature is designed for demons to send to
intermediate addresses, and not for humans to use, what does that
imply about rmail-resend?
Should we delete the rmail-resend command? Make it warn "This command
has counterintuitive results, since replies won't go to the other
recipients you resend to"? Make it add those recipients to the CC
list as well as putting them in Resent-to?
next prev parent reply other threads:[~2009-01-30 7:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 16:30 Change in rmail-reply Richard M Stallman
2009-01-26 17:39 ` Glenn Morris
2009-01-27 6:10 ` Richard M Stallman
2009-01-27 6:44 ` Don Armstrong
2009-01-27 18:18 ` Stefan Monnier
2009-01-27 22:58 ` Richard M Stallman
2009-01-27 23:22 ` Harald Hanche-Olsen
2009-01-29 14:32 ` Richard M Stallman
2009-01-29 15:08 ` Stefan Monnier
2009-01-29 16:36 ` Stephen J. Turnbull
2009-01-30 7:25 ` Richard M Stallman [this message]
2009-01-30 8:04 ` Stephen J. Turnbull
2009-01-30 23:05 ` Richard M Stallman
2009-01-31 0:50 ` Chetan Pandya
2009-01-31 1:01 ` Chetan Pandya
2009-01-31 3:16 ` Jason Rumney
2009-01-31 3:53 ` Chetan Pandya
2009-01-31 6:32 ` Stephen J. Turnbull
2009-01-31 9:52 ` Chetan Pandya
2009-02-01 6:30 ` Richard M Stallman
2009-01-31 3:18 ` Jason Rumney
2009-01-31 3:31 ` Jason Rumney
2009-02-01 6:30 ` Richard M Stallman
2009-01-31 4:57 ` Stephen J. Turnbull
2009-01-27 23:35 ` Don Armstrong
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=E1LSnl4-0002AP-C4@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.