From: Roger Pau Monne <roger.pau@citrix.com>
Date: Thu, 28 Sep 2017 18:57:56 +0000 (-0700)
Subject: Enable $reply_self for group-reply, even with $metoo unset.
X-Git-Tag: mutt-1-10-rel~127
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=cfcd87879a22df76934ea73a03d6c686ae715e00;p=mutt

Enable $reply_self for group-reply, even with $metoo unset.

For a (r)eply, the $metoo variable does not have any effect because
there is a single recipient.

However with (g)roup reply, the To was initially set to the sender,
but subsequently removed my $nometoo.  The empty To line is then
replaced with the Cc line, resulting in a (logically correct but)
surprising outcome.

Change the behavior such that $nometoo will not strip a single To
recipient when $reply_self is set.
---

diff --git a/send.c b/send.c
index 30821ecc..cae3bb08 100644
--- a/send.c
+++ b/send.c
@@ -592,7 +592,7 @@ void mutt_fix_reply_recipients (ENVELOPE *env)
      * the user is the only recipient, it ends up on the TO: field
      */
     env->cc = remove_user (env->cc, (env->to == NULL));
-    env->to = remove_user (env->to, (env->cc == NULL));
+    env->to = remove_user (env->to, (env->cc == NULL) || option (OPTREPLYSELF));
   }
   
   /* the CC field can get cluttered, especially with lists */