Re: [PATCH 1/3] cli: add insert --must-index option

diff --git a/9d/b3d4f7a3da87aac360d854f3cd33dbce42ee9b b/9d/b3d4f7a3da87aac360d854f3cd33dbce42ee9b
new file mode 100644 (file)
index 0000000..8d48090
--- /dev/null
+++ b/9d/b3d4f7a3da87aac360d854f3cd33dbce42ee9b
@@ -0,0 +1,88 @@
+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 1FE1D431FAF\r
+       for <notmuch@notmuchmail.org>; Fri, 26 Jul 2013 22:15:56 -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 eiUCUaYWHs7Z for <notmuch@notmuchmail.org>;\r
+       Fri, 26 Jul 2013 22:15:50 -0700 (PDT)\r
+Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com\r
+       [209.85.220.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 8BF59431FAE\r
+       for <notmuch@notmuchmail.org>; Fri, 26 Jul 2013 22:15:50 -0700 (PDT)\r
+Received: by mail-pa0-f45.google.com with SMTP id bg4so3968263pad.32\r
+       for <notmuch@notmuchmail.org>; Fri, 26 Jul 2013 22:15:49 -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:cc:subject:in-reply-to:references\r
+       :mime-version:content-type:content-disposition\r
+       :content-transfer-encoding;\r
+       bh=NmEEzZzb4J7NPcEaFchAlqRVdCCIymoDRMKd/LYIn8Y=;\r
+       b=VxcrzMjeSZoLm/B2AZ8B7wvh6R4M8BI5FolhvepRGXfFMftiFJ0SnmIhV0Lh2GQgwj\r
+       InuUh/VmzFWVKwG3z77iQUIYKAuKQFEUG2xpcCOBR0ZXNWckeeBy6WNl6k0wV7/8n8oE\r
+       qRIeQxfYqXod/jAg4ZzASrz93aGO3tLlnT5QFz4HhlBVqykr539juYL3Tsg8iUaM4C73\r
+       s9z2bdZdRV7jTq/vWQYQhDcQl9L+Q/02Cq0+XyuoW8BHmU5x+6C6VBG/JGsTqYo3ROjt\r
+       o9c//t0DcpTfGkT5/Nxf44P5+TyTrWZFI1ARLhGvVYXqysYR0jbrIGj2LIicBeYQS/vo\r
+       UcOA==\r
+X-Received: by 10.66.139.227 with SMTP id rb3mr58655066pab.121.1374902149707; \r
+       Fri, 26 Jul 2013 22:15:49 -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 ESMTPSA id 7sm7277904paf.22.2013.07.26.22.15.47\r
+       for <multiple recipients>\r
+       (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+       Fri, 26 Jul 2013 22:15:48 -0700 (PDT)\r
+Date: Sat, 27 Jul 2013 15:15:10 +1000\r
+Message-ID: <20130727151510.GA13750@hili.localdomain>\r
+From: Peter Wang <novalazy@gmail.com>\r
+To: Mark Walters <markwalters1009@gmail.com>\r
+Subject: Re: [PATCH 1/3] cli: add insert --must-index option\r
+In-Reply-To: <87ip048gbj.fsf@qmul.ac.uk>\r
+References: <1374365254-13227-1-git-send-email-novalazy@gmail.com>\r
+       <87ip048gbj.fsf@qmul.ac.uk>\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: Sat, 27 Jul 2013 05:15:56 -0000\r
+\r
+On Sun, 21 Jul 2013 09:31:28 +0100, Mark Walters <markwalters1009@gmail.com> wrote:\r
+> \r
+> Do you have a particular use case where indexing is required but tagging\r
+> is not? For my uses I would prefer failing if either indexing or tagging\r
+> failed. (My use being postponing messages; If they don't get the\r
+> postponed tag they could be hard to find)\r
+\r
+You're right.\r
+\r
+What about a failure to sync tags to maildir flags?\r
+\r
+I now noticed that database modifications aren't flushed until the\r
+notmuch_database_destroy call (right?), which has no return value and\r
+failure of which is silently ignored.  That's acceptable in the default\r
+mode, but with --must-index the failure should be reported (and the\r
+file deleted).\r
+\r
+Peter\r