1 Return-Path: <novalazy@gmail.com>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 1FE1D431FAF
\r
6 for <notmuch@notmuchmail.org>; Fri, 26 Jul 2013 22:15:56 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
\r
13 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id eiUCUaYWHs7Z for <notmuch@notmuchmail.org>;
\r
17 Fri, 26 Jul 2013 22:15:50 -0700 (PDT)
\r
18 Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com
\r
19 [209.85.220.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id 8BF59431FAE
\r
22 for <notmuch@notmuchmail.org>; Fri, 26 Jul 2013 22:15:50 -0700 (PDT)
\r
23 Received: by mail-pa0-f45.google.com with SMTP id bg4so3968263pad.32
\r
24 for <notmuch@notmuchmail.org>; Fri, 26 Jul 2013 22:15:49 -0700 (PDT)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
26 h=date:message-id:from:to:cc:subject:in-reply-to:references
\r
27 :mime-version:content-type:content-disposition
\r
28 :content-transfer-encoding;
\r
29 bh=NmEEzZzb4J7NPcEaFchAlqRVdCCIymoDRMKd/LYIn8Y=;
\r
30 b=VxcrzMjeSZoLm/B2AZ8B7wvh6R4M8BI5FolhvepRGXfFMftiFJ0SnmIhV0Lh2GQgwj
\r
31 InuUh/VmzFWVKwG3z77iQUIYKAuKQFEUG2xpcCOBR0ZXNWckeeBy6WNl6k0wV7/8n8oE
\r
32 qRIeQxfYqXod/jAg4ZzASrz93aGO3tLlnT5QFz4HhlBVqykr539juYL3Tsg8iUaM4C73
\r
33 s9z2bdZdRV7jTq/vWQYQhDcQl9L+Q/02Cq0+XyuoW8BHmU5x+6C6VBG/JGsTqYo3ROjt
\r
34 o9c//t0DcpTfGkT5/Nxf44P5+TyTrWZFI1ARLhGvVYXqysYR0jbrIGj2LIicBeYQS/vo
\r
36 X-Received: by 10.66.139.227 with SMTP id rb3mr58655066pab.121.1374902149707;
\r
37 Fri, 26 Jul 2013 22:15:49 -0700 (PDT)
\r
38 Received: from localhost (215.42.233.220.static.exetel.com.au.
\r
40 by mx.google.com with ESMTPSA id 7sm7277904paf.22.2013.07.26.22.15.47
\r
41 for <multiple recipients>
\r
42 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
\r
43 Fri, 26 Jul 2013 22:15:48 -0700 (PDT)
\r
44 Date: Sat, 27 Jul 2013 15:15:10 +1000
\r
45 Message-ID: <20130727151510.GA13750@hili.localdomain>
\r
46 From: Peter Wang <novalazy@gmail.com>
\r
47 To: Mark Walters <markwalters1009@gmail.com>
\r
48 Subject: Re: [PATCH 1/3] cli: add insert --must-index option
\r
49 In-Reply-To: <87ip048gbj.fsf@qmul.ac.uk>
\r
50 References: <1374365254-13227-1-git-send-email-novalazy@gmail.com>
\r
51 <87ip048gbj.fsf@qmul.ac.uk>
\r
53 Content-Type: text/plain; charset=utf-8
\r
54 Content-Disposition: inline
\r
55 Content-Transfer-Encoding: 8bit
\r
56 Cc: notmuch@notmuchmail.org
\r
57 X-BeenThere: notmuch@notmuchmail.org
\r
58 X-Mailman-Version: 2.1.13
\r
60 List-Id: "Use and development of the notmuch mail system."
\r
61 <notmuch.notmuchmail.org>
\r
62 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
63 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
64 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
65 List-Post: <mailto:notmuch@notmuchmail.org>
\r
66 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
67 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
68 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
69 X-List-Received-Date: Sat, 27 Jul 2013 05:15:56 -0000
\r
71 On Sun, 21 Jul 2013 09:31:28 +0100, Mark Walters <markwalters1009@gmail.com> wrote:
\r
73 > Do you have a particular use case where indexing is required but tagging
\r
74 > is not? For my uses I would prefer failing if either indexing or tagging
\r
75 > failed. (My use being postponing messages; If they don't get the
\r
76 > postponed tag they could be hard to find)
\r
80 What about a failure to sync tags to maildir flags?
\r
82 I now noticed that database modifications aren't flushed until the
\r
83 notmuch_database_destroy call (right?), which has no return value and
\r
84 failure of which is silently ignored. That's acceptable in the default
\r
85 mode, but with --must-index the failure should be reported (and the
\r