unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH 1/2] notmuch-reply: Add support for replying only to sender
Date: Tue, 09 Mar 2010 10:25:58 -0800	[thread overview]
Message-ID: <87zl2hic7d.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <87ws0ujcv0.fsf@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]

On Fri, 11 Dec 2009 11:01:15 +0530, "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com> wrote:
> On Fri, 04 Dec 2009 11:07:54 -0800, Carl Worth <cworth@cworth.org> wrote:
> > On Thu,  3 Dec 2009 14:16:44 +0530, "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:
> > > 
> > > This patch add --format=sender-only option.
> > 
> > I like the idea here, (and agree that an 'R' keybinding would be great).
> > 
> > But surely there's a way to implement this with dramatically less code
> > duplication?
> 
> I sent an updated patch which did the above with less code duplication. Any
> chance of getting this merged ?

Thanks for the updated patch, (and I sincerely apologize for my late
response).

I still like the functionality and keybinding, and it's great to see
less code duplication in this patch, but I also agree with the point Jed
made:

  I think --format= should not be used for this, formatting is orthogonal
  to selecting recipients.

We're already using --format for selection JSON output, for example. And
it's not totally unreasonable to expect that someone might want JSON
output from "notmuch reply" as well. So let's use a separate option
here.

Perhaps:

	--recipient=all|sender

or so?

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2010-03-09 19:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03  8:46 [PATCH 1/2] notmuch-reply: Add support for replying only to sender Aneesh Kumar K.V
2009-12-03  8:46 ` [PATCH 2/2] notmuch.el: Add support for reply-to sender Aneesh Kumar K.V
2009-12-04 19:07 ` [PATCH 1/2] notmuch-reply: Add support for replying only to sender Carl Worth
2009-12-04 19:21   ` Jed Brown
2009-12-11  5:31   ` Aneesh Kumar K. V
2010-03-09 18:25     ` Carl Worth [this message]
2010-03-10 16:31       ` [PATCH -V3 " Aneesh Kumar K.V
2010-03-11 12:45         ` Michal Sojka
2010-03-10 16:31       ` [PATCH -V3 2/2] notmuch.el: Add support for reply-to sender Aneesh Kumar K.V
2009-12-05  9:37 ` [PATCH -V2] notmuch-reply: Add support for replying only to sender Aneesh Kumar K.V
  -- strict thread matches above, loose matches on Subject: below --
2010-04-06  7:11 [PATCH -V2 1/2] " Sebastian Spaeth
2010-04-06  7:12 ` [PATCH " Sebastian Spaeth

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=87zl2hic7d.fsf@yoom.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=aneesh.kumar@gmail.com \
    --cc=aneesh.kumar@linux.vnet.ibm.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).