From: Jani Nikula <jani@nikula.org>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/3] Allow widen reply
Date: Sun, 12 May 2013 23:53:37 +0300 [thread overview]
Message-ID: <878v3japim.fsf@nikula.org> (raw)
In-Reply-To: <1368303344-13713-1-git-send-email-markwalters1009@gmail.com>
Hi Mark -
On Sat, 11 May 2013, Mark Walters <markwalters1009@gmail.com> wrote:
> This is an initial draft of a patch to allow the emacs frontend to
> "widen" the reply: i.e., change the headers to reply-to-all after a
> reply-to-sender has been started.
I didn't look at the patches very much, but I like the idea, a lot. This
is the way it should be.
> There are some things that need to be worked out: do we want to allow
> narrowing the reply (ie going from reply-to-all back to
> reply-to-sender)? I did not implement this as it was slightly easier
> not to, message-mode doesn't have this by default, and it's easy for a
> user to remove recipients.
Might be useful, but can be added later on.
The same for better handling of mail-followup-to: and reply-to:. For
those, I'm not sure if a keybinding for "widening" the recipients is the
right choice, as they both mean *changing*, not necessarily widening the
recipient list. Maybe you can come up with an approach here that extends
well to those too later on. ;)
BR,
Jani.
prev parent reply other threads:[~2013-05-12 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 20:15 [PATCH 0/3] Allow widen reply Mark Walters
2013-05-11 20:15 ` [PATCH 1/3] cli: show: separate out the printing of recipient headers Mark Walters
2013-05-11 20:15 ` [PATCH 2/3] cli: reply: additionally output reply-to-all headers to allow widen reply Mark Walters
2013-05-11 20:15 ` [PATCH 3/3] emacs: mua: allow the user to widen the reply Mark Walters
2013-05-12 20:53 ` Jani Nikula [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
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=878v3japim.fsf@nikula.org \
--to=jani@nikula.org \
--cc=markwalters1009@gmail.com \
--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).