Re: Notmuch Pick

diff --git a/86/0f96a1ca3892bec06f5f3da4736e54f862a757 b/86/0f96a1ca3892bec06f5f3da4736e54f862a757
new file mode 100644 (file)
index 0000000..ded96a0
--- /dev/null
+++ b/86/0f96a1ca3892bec06f5f3da4736e54f862a757
@@ -0,0 +1,82 @@
+Return-Path: <novalazy@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 CD624431FB6\r
+       for <notmuch@notmuchmail.org>; Tue, 19 Jun 2012 18:01:54 -0700 (PDT)\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 T1v6nl3vfGHO for <notmuch@notmuchmail.org>;\r
+       Tue, 19 Jun 2012 18:01:54 -0700 (PDT)\r
+Received: from mail-pb0-f53.google.com (mail-pb0-f53.google.com\r
+       [209.85.160.53]) (using TLSv1 with cipher RC4-MD5 (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 3F36E431FAF\r
+       for <notmuch@notmuchmail.org>; Tue, 19 Jun 2012 18:01:54 -0700 (PDT)\r
+Received: by pbbrr13 with SMTP id rr13so12887502pbb.26\r
+       for <notmuch@notmuchmail.org>; Tue, 19 Jun 2012 18:01:52 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=date:message-id:from:to:subject:in-reply-to:references:mime-version\r
+       :content-type:content-disposition:content-transfer-encoding;\r
+       bh=tlDt/Wltdq1yAxUtKMkpAF+vivxXzIt/tmLLICpwOjY=;\r
+       b=LI1jqAtBU1B96WzwSCtPnvVGWqpXXDr443AQkttW8NFGG+vP9Sqo4KKCafD6O/ozBV\r
+       z6WHS9Y5VnWwEwWenJR2CXRBzWS6cACNKnolU7vKYsaOVdlLsGZlaP7Jx8tKMkNObRqS\r
+       2UDp+RHAeaduYIZHPyHMoE0FY6btNTMyFRpl6Gt+UYc2Y6fbmFLRdtmH6NF7MGhaRsGd\r
+       XH19YTBO0/AcNWHJ8rA7pZIcNEuiByE1G2FizMRnOHjNYo9VtfaDH5VqhasEIbxk2efH\r
+       fLEi9rA3sGwx258M28lcdjgT6uAupVu9IpY72ERxiNQ/jNoBmdGz/s+QMw5VvOQq7Xsn\r
+       1UCA==\r
+Received: by 10.68.226.99 with SMTP id rr3mr69605104pbc.48.1340154112219;\r
+       Tue, 19 Jun 2012 18:01:52 -0700 (PDT)\r
+Received: from localhost (215.42.233.220.static.exetel.com.au.\r
+       [220.233.42.215])\r
+       by mx.google.com with ESMTPS id ob9sm29805404pbb.28.2012.06.19.18.01.47\r
+       (version=TLSv1/SSLv3 cipher=OTHER);\r
+       Tue, 19 Jun 2012 18:01:50 -0700 (PDT)\r
+Date: Wed, 20 Jun 2012 11:01:39 +1000\r
+Message-ID: <20120620110139.GA2356@hili.localdomain>\r
+From: Peter Wang <novalazy@gmail.com>\r
+To: notmuch@notmuchmail.org\r
+Subject: Re: Notmuch Pick\r
+In-Reply-To: <87zk7z2kz2.fsf@servo.finestructure.net>\r
+References: <87395ump0d.fsf@qmul.ac.uk>\r
+       <87zk80ilt9.fsf@servo.finestructure.net>\r
+       <87mx3zok3d.fsf@qmul.ac.uk>\r
+       <87zk7z2kz2.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: 8bit\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, 20 Jun 2012 01:01:55 -0000\r
+\r
+On Tue, 19 Jun 2012 11:52:01 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:\r
+> \r
+> So I think it would be nice and clean if the default json output\r
+> included all the message headers and the message structure, and then\r
+> part contents could be retrieved individually.  I imagine show mode\r
+> could be restructured such that it could use this efficiently.\r
+\r
+Whatever is done, please keep the option to return all message bodies at\r
+once, at least for short threads (the common case).  I want them anyway.\r
+Don't force me to make N separate requests, especially over a high\r
+latency link.\r
+\r
+Peter\r