MIME-Version: 1.0
Sender: awg@xvx.ca
In-Reply-To: <cover.1325794371.git.jani@nikula.org>
References: <cover.1325794371.git.jani@nikula.org>
Date: Thu, 5 Jan 2012 17:01:44 -0700
Message-ID:
 <CAMoJFUtby4_oRSwWfW6_OpPuMEEPvyLgtbRmSNxL-0ODjWgijA@mail.gmail.com>
Subject: Re: [PATCH 0/4] notmuch reply bugfix & reply to sender only
From: Adam Wolfe Gordon <awg+notmuch@xvx.ca>
To: Jani Nikula <jani@nikula.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: notmuch@notmuchmail.org
Precedence: list

On Thu, Jan 5, 2012 at 13:25, Jani Nikula <jani@nikula.org> wrote:
> Bikeshedding topic #1: How about making replying to just the sender the default
> in "notmuch reply", and having --reply-all option (instead of --no-reply-all)?
>
> Bikeshedding topic #2: How about binding 'r' to reply to just the sender by
> default, and making 'R' reply-all (instead of vice versa)?

I like both these suggestions.  This would bring the notmuch behavior
in line with gmail, which is what I tend to expect.

Mark Walters brings up a good point, that there is a question of what
to do when the user tries to reply to their own email.  When I do
this, what I intend is to send another email to the last person I
emailed in the thread, so I think the suggested heuristic of looking
at other headers would work.  But, maybe others have a different
expectation in this case?