Return-Path: <novalazy@gmail.com>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id 13BA9429E36
	for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 13:08:52 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=disabled
Received: from olra.theworths.org ([127.0.0.1])
	by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CjuKGYw8FT5y for <notmuch@notmuchmail.org>;
	Sun, 12 Jan 2014 13:08:44 -0800 (PST)
Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com
	[209.85.192.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by olra.theworths.org (Postfix) with ESMTPS id 985E8429E2F
	for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 13:08:44 -0800 (PST)
Received: by mail-pd0-f178.google.com with SMTP id v10so131037pde.9
	for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 13:08:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=date:message-id:from:to:cc:subject:in-reply-to:references
	:mime-version:content-type:content-disposition
	:content-transfer-encoding;
	bh=W/wnqkcv36X2bzLd75ma5eD9q7LCzMqrCf8GtHDWBXQ=;
	b=ye9py7dDqUavMqF7/pkddxAnOj0NzjDduojDVUrcYcN1JCzCv8uziJPbsC8Zmw0wPq
	BOcpQg+ABE7kXGsq8qCk1DalBmLwHv7lzD/maaM95AgPTP2OgILcqV7lxQwPlOtv55An
	5yP8DFouJWhLwGanrBFEGX4vYFsaGRZLSyMDIO4krtb73ilkrot846CBmlwm3ywE9uBt
	uE7TPI5tdGFpDtfDkpUdL9u6ykAuTRak5zBGNZfyhefsEmIYnKrD2pXuT1NC6coRoBWc
	1KCqai/dqRHP/SWbhklVi0qeRNCk6YEMEhp2j1KsVhKFwtQ+v9oztMwjBfP6FFuIpnWF
	oPvg==
X-Received: by 10.68.92.98 with SMTP id cl2mr25595444pbb.81.1389560922571;
	Sun, 12 Jan 2014 13:08:42 -0800 (PST)
Received: from localhost (215.42.233.220.static.exetel.com.au.
	[220.233.42.215]) by mx.google.com with ESMTPSA id
	gv10sm32962664pbd.0.2014.01.12.13.08.39 for <multiple recipients>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Sun, 12 Jan 2014 13:08:41 -0800 (PST)
Date: Mon, 13 Jan 2014 08:08:36 +1100
Message-ID: <20140113080836.GA1138@hili.localdomain>
From: Peter Wang <novalazy@gmail.com>
To: Jani Nikula <jani@nikula.org>
Subject: Re: [PATCH] show: add In-reply-to,
	References fields to structured formats
In-Reply-To: <878uulush7.fsf@nikula.org>
References: <1389502800-9237-1-git-send-email-novalazy@gmail.com>
	<878uulush7.fsf@nikula.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Cc: notmuch@notmuchmail.org
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jan 2014 21:08:52 -0000

On Sun, 12 Jan 2014 17:31:32 +0200, Jani Nikula <jani@nikula.org> wrote:
> On Sun, 12 Jan 2014, Peter Wang <novalazy@gmail.com> wrote:
> > This is useful when 'show' is used to retrieve a draft message
> > which is in reply to another message.
> 
> I'd like to know more about *how* this is useful. Indeed the whole big
> picture about supporting draft or postponed messages is foggy. I would
> like to have some clarity about that first.
> 
> Apparently the idea is to index draft messages. How do you save them?
> What guarantees are there that they look enough like real messages that
> they get indexed? Does this patch mean that the idea is to resume draft
> messages using the structured formats instead of opening the raw file?
> Why?  What do you plan to do with the saved draft? And so on...

I didn't realise storing drafts in your Maildir was unusual.

A draft message (including its attachments) may be added to a Maildir
folder with notmuch insert or notmuch-deliver, and then tagged.
The message must look enough like a real message for indexing but it is
not hard for an email client to arrange -- the message is ostensibly to
be sent anyway.  Unlike saving in a local file, keeping the draft in a
central mail store means it will be accessible anywhere that you can
access the rest of your mail.

Draft messages may be retrieved for previewing or resumption with
notmuch show, like other messages.  The raw file may be on another
machine so it is not always possible to read it directly.  The advantage
of using a structured output format instead of the raw output format is
the same as for any other message -- notmuch has already parsed it for
you.  The disadvantage is that notmuch show's structured output only
presents a subset of headers, so other headers will be lost.
(This suggests an alternative change if notmuch maintainers are
receptive.)

Indexed draft messages will, by default, show up in normal display
so they will need to be hidden with notmuch search exclusions.
Drafts may tagged with 'delete' for eventual removal.

Peter