Re: [Patch v2 0/4] Control selection of From: header when replying

diff --git a/0f/b87c3451d0e666d521f0911d4e67e7dd9ea80b b/0f/b87c3451d0e666d521f0911d4e67e7dd9ea80b
new file mode 100644 (file)
index 0000000..6aece04
--- /dev/null
+++ b/0f/b87c3451d0e666d521f0911d4e67e7dd9ea80b
@@ -0,0 +1,98 @@
+Return-Path: <dmitry.kurochkin@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id E9852431FAF\r
+       for <notmuch@notmuchmail.org>; Sat,  4 Feb 2012 22:59:24 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.799\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+       FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id uB3PIoI4Omfr for <notmuch@notmuchmail.org>;\r
+       Sat,  4 Feb 2012 22:59:24 -0800 (PST)\r
+Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com\r
+       [209.85.214.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 25D61431FAE\r
+       for <notmuch@notmuchmail.org>; Sat,  4 Feb 2012 22:59:23 -0800 (PST)\r
+Received: by bke11 with SMTP id 11so4645800bke.26\r
+       for <notmuch@notmuchmail.org>; Sat, 04 Feb 2012 22:59:21 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;\r
+       h=from:to:cc:subject:in-reply-to:references:user-agent:date\r
+       :message-id:mime-version:content-type;\r
+       bh=ANKQl7oADfNLZsOxteQJ0UVjCeDUl+9/8CFw9GRlobQ=;\r
+       b=C4WimUSB0m+dpkbie5/jTEPF6Cdx3fxVyn+DG0a3nksY6qoRSuPcun1DjtKvJUlUry\r
+       mFaQjLnw2YKbY7n0BilqjLKDLcb3d+79X7i4ELKKRotjM4MBr40YqgOE8MiA0hTfysRJ\r
+       k/3YKqpp7hIBDEQVoA1Fz6knG1VjkNy16UtoY=\r
+Received: by 10.204.173.11 with SMTP id n11mr6305473bkz.120.1328425161371;\r
+       Sat, 04 Feb 2012 22:59:21 -0800 (PST)\r
+Received: from localhost ([91.144.186.21])\r
+       by mx.google.com with ESMTPS id o26sm32855911bko.14.2012.02.04.22.59.19\r
+       (version=TLSv1/SSLv3 cipher=OTHER);\r
+       Sat, 04 Feb 2012 22:59:20 -0800 (PST)\r
+From: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>\r
+To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org\r
+Subject: Re: [Patch v2 0/4] Control selection of From: header when replying\r
+In-Reply-To: <1328388317-20161-1-git-send-email-markwalters1009@gmail.com>\r
+References: <1328388317-20161-1-git-send-email-markwalters1009@gmail.com>\r
+User-Agent: Notmuch/0.11+139~gd9b7cab (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sun, 05 Feb 2012 10:58:04 +0400\r
+Message-ID: <87ipjlix6r.fsf@gmail.com>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 05 Feb 2012 06:59:25 -0000\r
+\r
+Hi Mark.\r
+\r
+I am not sure I like this solution.  My concerns are:\r
+\r
+* New option looks too complex, too specific.\r
+\r
+* There are more aspects of notmuch reply behavior which users would\r
+  like to change (e.g. which part to quote).  If we add an option for\r
+  each, we complicate both nomtuch show UI and code.\r
+\r
+The problem is that notmuch show output format is too limiting.  Instead\r
+of providing myriad of options for tweaking notmuch show text format\r
+behavior, we should add JSON format for notmuch reply similar to nomtuch\r
+show.  That would allow notmuch reply to produce structured output with\r
+required additional information, which should be enough for users to\r
+construct whatever reply they want.\r
+\r
+In this particular case, notmuch reply JSON format could have\r
+"from-source" attribute that would indicate how it was guessed.\r
+\r
+Now the best part.  Not so long ago, Adam (in Cc) provided a patch for\r
+improving nomtuch reply for HTML-only emails.  At first he added an\r
+option for notmuch reply, like you did for from-guessing.  I suggested\r
+him to implement it based on the JSON format instead and he did.  AFAIK\r
+the latest version of his patches is [1].  I did not look at the code\r
+though.  It seems that it is waiting for more review.\r
+\r
+So, instead of adding more nomtuch show options, I think a better\r
+solution is to work with Adam to get the notmuch reply JSON format to\r
+master and then fix the from-guessing issue by adding an attribute to\r
+notmuch reply JSON format.\r
+\r
+Regards,\r
+  Dmitry\r
+\r
+[1] id:"1326995217-27423-1-git-send-email-awg+notmuch@xvx.ca"\r