--- /dev/null
+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 13BA9429E36\r
+ for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 13:08:52 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.099\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.099 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_NONE=-0.0001] 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 CjuKGYw8FT5y for <notmuch@notmuchmail.org>;\r
+ Sun, 12 Jan 2014 13:08:44 -0800 (PST)\r
+Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com\r
+ [209.85.192.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 985E8429E2F\r
+ for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 13:08:44 -0800 (PST)\r
+Received: by mail-pd0-f178.google.com with SMTP id v10so131037pde.9\r
+ for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 13:08:42 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=date:message-id:from:to:cc:subject:in-reply-to:references\r
+ :mime-version:content-type:content-disposition\r
+ :content-transfer-encoding;\r
+ bh=W/wnqkcv36X2bzLd75ma5eD9q7LCzMqrCf8GtHDWBXQ=;\r
+ b=ye9py7dDqUavMqF7/pkddxAnOj0NzjDduojDVUrcYcN1JCzCv8uziJPbsC8Zmw0wPq\r
+ BOcpQg+ABE7kXGsq8qCk1DalBmLwHv7lzD/maaM95AgPTP2OgILcqV7lxQwPlOtv55An\r
+ 5yP8DFouJWhLwGanrBFEGX4vYFsaGRZLSyMDIO4krtb73ilkrot846CBmlwm3ywE9uBt\r
+ uE7TPI5tdGFpDtfDkpUdL9u6ykAuTRak5zBGNZfyhefsEmIYnKrD2pXuT1NC6coRoBWc\r
+ 1KCqai/dqRHP/SWbhklVi0qeRNCk6YEMEhp2j1KsVhKFwtQ+v9oztMwjBfP6FFuIpnWF\r
+ oPvg==\r
+X-Received: by 10.68.92.98 with SMTP id cl2mr25595444pbb.81.1389560922571;\r
+ Sun, 12 Jan 2014 13:08:42 -0800 (PST)\r
+Received: from localhost (215.42.233.220.static.exetel.com.au.\r
+ [220.233.42.215]) by mx.google.com with ESMTPSA id\r
+ gv10sm32962664pbd.0.2014.01.12.13.08.39 for <multiple recipients>\r
+ (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Sun, 12 Jan 2014 13:08:41 -0800 (PST)\r
+Date: Mon, 13 Jan 2014 08:08:36 +1100\r
+Message-ID: <20140113080836.GA1138@hili.localdomain>\r
+From: Peter Wang <novalazy@gmail.com>\r
+To: Jani Nikula <jani@nikula.org>\r
+Subject: Re: [PATCH] show: add In-reply-to,\r
+ References fields to structured formats\r
+In-Reply-To: <878uulush7.fsf@nikula.org>\r
+References: <1389502800-9237-1-git-send-email-novalazy@gmail.com>\r
+ <878uulush7.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: 8bit\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: Sun, 12 Jan 2014 21:08:52 -0000\r
+\r
+On Sun, 12 Jan 2014 17:31:32 +0200, Jani Nikula <jani@nikula.org> wrote:\r
+> On Sun, 12 Jan 2014, Peter Wang <novalazy@gmail.com> wrote:\r
+> > This is useful when 'show' is used to retrieve a draft message\r
+> > which is in reply to another message.\r
+> \r
+> I'd like to know more about *how* this is useful. Indeed the whole big\r
+> picture about supporting draft or postponed messages is foggy. I would\r
+> like to have some clarity about that first.\r
+> \r
+> Apparently the idea is to index draft messages. How do you save them?\r
+> What guarantees are there that they look enough like real messages that\r
+> they get indexed? Does this patch mean that the idea is to resume draft\r
+> messages using the structured formats instead of opening the raw file?\r
+> Why? What do you plan to do with the saved draft? And so on...\r
+\r
+I didn't realise storing drafts in your Maildir was unusual.\r
+\r
+A draft message (including its attachments) may be added to a Maildir\r
+folder with notmuch insert or notmuch-deliver, and then tagged.\r
+The message must look enough like a real message for indexing but it is\r
+not hard for an email client to arrange -- the message is ostensibly to\r
+be sent anyway. Unlike saving in a local file, keeping the draft in a\r
+central mail store means it will be accessible anywhere that you can\r
+access the rest of your mail.\r
+\r
+Draft messages may be retrieved for previewing or resumption with\r
+notmuch show, like other messages. The raw file may be on another\r
+machine so it is not always possible to read it directly. The advantage\r
+of using a structured output format instead of the raw output format is\r
+the same as for any other message -- notmuch has already parsed it for\r
+you. The disadvantage is that notmuch show's structured output only\r
+presents a subset of headers, so other headers will be lost.\r
+(This suggests an alternative change if notmuch maintainers are\r
+receptive.)\r
+\r
+Indexed draft messages will, by default, show up in normal display\r
+so they will need to be hidden with notmuch search exclusions.\r
+Drafts may tagged with 'delete' for eventual removal.\r
+\r
+Peter\r
projects / notmuch-archives.git / commitdiff