From: Jani Nikula <jani@nikula.org>
To: notmuch@notmuchmail.org
Subject: [PATCH v2 0/3] cli: mail-followup-to support
Date: Sat, 30 Mar 2013 16:21:19 +0200 [thread overview]
Message-ID: <cover.1364652420.git.jani@nikula.org> (raw)
This is v2 of [1], rebased against master and with a better commit
message for patch 1/3. Patch 1/3 is trivial cleanup and IMO could just
be merged. There was debate on the actual stuff 2/3 and 3/3 [2].
I don't think adding a --reply-to=list option to notmuch reply is a good
idea. We should just do the right thing and keep the cli simple. Perhaps
we should drop the configuration (patch 2/3) altogether, and just
support mail-followup-to?
Or, perhaps notmuch reply should return *all* options in json, and let
the UI decide. Above all, let the UI change the reply style while
editing the reply. I'd probably like this approach most, more than these
patches, but I don't have the time to do it.
Here are the patches anyway; perhaps they could be an intermediate step,
or just a reference for anyone willing to do the above.
BR,
Jani.
[1] id:5eaa3acc22ee5513bdce5ab931b7a79ade880e06.1362254104.git.jani@nikula.org
[2] id:20130303120745.GA4884@hili.localdomain
Jani Nikula (3):
cli: config: remove unnecessary braces from if blocks
cli: add reply.honor_followup_to configuration option
cli: support Mail-Followup-To: in notmuch reply
notmuch-client.h | 7 +++++++
notmuch-config.c | 56 ++++++++++++++++++++++++++++++++++++++++++------------
notmuch-reply.c | 25 ++++++++++++++++++++++--
3 files changed, 74 insertions(+), 14 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-03-30 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 14:21 Jani Nikula [this message]
2013-03-30 14:21 ` [PATCH v2 1/3] cli: config: remove unnecessary braces from if blocks Jani Nikula
2013-03-30 22:36 ` David Bremner
2013-03-30 14:21 ` [PATCH v2 2/3] cli: add reply.honor_followup_to configuration option Jani Nikula
2013-03-30 14:21 ` [PATCH v2 3/3] cli: support Mail-Followup-To: in notmuch reply Jani Nikula
2013-05-11 20:05 ` [PATCH v2 0/3] cli: mail-followup-to support Mark Walters
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=cover.1364652420.git.jani@nikula.org \
--to=jani@nikula.org \
--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).