Re: [alot] reply from search mode
authorAdam Wolfe Gordon <awg+notmuch@xvx.ca>
Wed, 7 Mar 2012 14:21:45 +0000 (07:21 +1700)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:45:17 +0000 (09:45 -0800)
29/d077f77027a1eba7db093f1dafbbc61364bb2c [new file with mode: 0644]

diff --git a/29/d077f77027a1eba7db093f1dafbbc61364bb2c b/29/d077f77027a1eba7db093f1dafbbc61364bb2c
new file mode 100644 (file)
index 0000000..84e0c00
--- /dev/null
@@ -0,0 +1,72 @@
+Return-Path: <awg@xvx.ca>\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 33ADC431FBC\r
+       for <notmuch@notmuchmail.org>; Wed,  7 Mar 2012 06:21:48 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[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 QsL7raW+xGH5 for <notmuch@notmuchmail.org>;\r
+       Wed,  7 Mar 2012 06:21:47 -0800 (PST)\r
+Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com\r
+ [74.125.83.53])       (using TLSv1 with cipher RC4-SHA (128/128 bits))        (No client\r
+ certificate requested)        by olra.theworths.org (Postfix) with ESMTPS id\r
+ 78934431FAE   for <notmuch@notmuchmail.org>; Wed,  7 Mar 2012 06:21:47 -0800\r
+ (PST)\r
+Received: by eekb47 with SMTP id b47so3264144eek.26\r
+       for <notmuch@notmuchmail.org>; Wed, 07 Mar 2012 06:21:46 -0800 (PST)\r
+MIME-Version: 1.0\r
+Received: by 10.112.82.6 with SMTP id e6mr803733lby.31.1331130106050; Wed, 07\r
+       Mar 2012 06:21:46 -0800 (PST)\r
+Sender: awg@xvx.ca\r
+Received: by 10.112.109.234 with HTTP; Wed, 7 Mar 2012 06:21:45 -0800 (PST)\r
+X-Originating-IP: [96.52.216.56]\r
+In-Reply-To: <20120306211747.31898.21772@brick.lan>\r
+References: <20120306160016.2673.36080@plc.plecavalier.com>\r
+       <20120306211747.31898.21772@brick.lan>\r
+Date: Wed, 7 Mar 2012 07:21:45 -0700\r
+X-Google-Sender-Auth: fNxWfj66jbu_A_oA4OedkYYpcNM\r
+Message-ID:\r
+ <CAMoJFUsbq-cYHKJ2F5PRZuww7q-u_DBQNvpUfXj_Z-BBUfb8Kw@mail.gmail.com>\r
+Subject: Re: [alot] reply from search mode\r
+From: Adam Wolfe Gordon <awg+notmuch@xvx.ca>\r
+To: Patrick Totzke <patricktotzke@googlemail.com>\r
+Content-Type: text/plain; charset=ISO-8859-1\r
+X-Gm-Message-State:\r
+ ALoCoQlbocWlHm4jzJfUCdjy02UNEuh/5Vmmwi64UPsgAeBU9u2rA9D9ntnDr/0rJqYsbKGSFTO6\r
+Cc: notmuch@notmuchmail.org\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: Wed, 07 Mar 2012 14:21:48 -0000\r
+\r
+On Tue, Mar 6, 2012 at 14:17, Patrick Totzke\r
+<patricktotzke@googlemail.com> wrote:\r
+> Quoting Philippe LeCavalier (2012-03-06 16:00:16)\r
+>>How would I add a reply key binding to reply directly from the search\r
+>>mode. ie something like R. Forward and editnew would be nice as well.\r
+>\r
+> This could indeed be useful, but I'm not convinced this is a great idea in general:\r
+> What would that command do if your selection is a thread with multiple leaf-mails?\r
+> reply to the first? ask the user?\r
+\r
+It's worth noting that this question is unresolved for Notmuch in\r
+general. My reply patchset disables the CLI reply command for searches\r
+returning multiple messages, which will also disable this\r
+functionality in emacs. Right now it "works", but doesn't really\r
+produce desirable behavior.\r