Re: [notmuch] Asynchronous tagging

diff --git a/54/c220748a5c1f2dc4bcbe805a4841e91f4ddfb9 b/54/c220748a5c1f2dc4bcbe805a4841e91f4ddfb9
new file mode 100644 (file)
index 0000000..bc054d7
--- /dev/null
+++ b/54/c220748a5c1f2dc4bcbe805a4841e91f4ddfb9
@@ -0,0 +1,100 @@
+Return-Path: <five9a2@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 14E59431FAE\r
+       for <notmuch@notmuchmail.org>; Sat, 21 Nov 2009 13:17:09 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\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 1qreFow0QL01 for <notmuch@notmuchmail.org>;\r
+       Sat, 21 Nov 2009 13:17:07 -0800 (PST)\r
+Received: from mail-bw0-f224.google.com (mail-bw0-f224.google.com\r
+       [209.85.218.224])\r
+       by olra.theworths.org (Postfix) with ESMTP id E01ED431FBC\r
+       for <notmuch@notmuchmail.org>; Sat, 21 Nov 2009 13:17:06 -0800 (PST)\r
+Received: by bwz24 with SMTP id 24so3133256bwz.30\r
+       for <notmuch@notmuchmail.org>; Sat, 21 Nov 2009 13:17:06 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;\r
+       h=domainkey-signature:received:received:sender:from:to:subject\r
+       :in-reply-to:references:date:message-id:mime-version:content-type;\r
+       bh=Yj/rxRlPV1Em55E7qy2CofH1nUWEY90XhNQRVOhddAw=;\r
+       b=o8zmGlKmmCKQ0aqN173tZUAk2UyuYOnn6iTTPZxu/HGixn982wtc+y5Gr6Jw32XvDB\r
+       1rMnRyWBAaGPf0nwtPzHVzGNhQk4oX3HiT8YL/JhTSgIqLaeqGRTAEv4IUY5Q2i6DDAu\r
+       3ezeXDyAAKaWtXHGaTKf/I4bf66rMoN0Ta1IE=\r
+DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;\r
+       h=sender:from:to:subject:in-reply-to:references:date:message-id\r
+       :mime-version:content-type;\r
+       b=cVfpFteZfHjkpDE1QDNJc6F7+dazVvT9pi2snrYIL2lwS+RTQpxmuIrl03RJBQDOyJ\r
+       ZAtvWyuGOcz8d15cnsqIzHiQgTFdznlz2dugtVourfL/Da9y5hfIrphuiIs42/eyCeKv\r
+       LiYB3ywXMvOhoXkWUKqget7uCjw27G373dxG8=\r
+Received: by 10.204.34.70 with SMTP id k6mr2898538bkd.178.1258838225984;\r
+       Sat, 21 Nov 2009 13:17:05 -0800 (PST)\r
+Received: from kunyang (vawpc43.ethz.ch [129.132.59.11])\r
+       by mx.google.com with ESMTPS id 26sm3390189fks.50.2009.11.21.13.17.04\r
+       (version=TLSv1/SSLv3 cipher=RC4-MD5);\r
+       Sat, 21 Nov 2009 13:17:04 -0800 (PST)\r
+Sender: Jed Brown <five9a2@gmail.com>\r
+From: Jed Brown <jed@59A2.org>\r
+To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org\r
+In-Reply-To: <87tywn386a.fsf@yoom.home.cworth.org>\r
+References: <87fx87u3no.fsf@59A2.org> <87einru0f9.fsf@59A2.org>\r
+       <87tywn386a.fsf@yoom.home.cworth.org>\r
+Date: Sat, 21 Nov 2009 22:17:34 +0100\r
+Message-ID: <87aayftw5t.fsf@59A2.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Subject: Re: [notmuch] Asynchronous tagging\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.12\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, 21 Nov 2009 21:17:09 -0000\r
+\r
+On Sat, 21 Nov 2009 22:00:13 +0100, Carl Worth <cworth@cworth.org> wrote:\r
+> Ah, OK. So you made a change on the Gmail side and that caused a file to\r
+> be renamed locally.\r
+\r
+yes\r
+\r
+> Or did you mean you removed the tag from within emacs? In that case, the\r
+> search term used to find the message is the message id itself. (Try\r
+> running "M-x visible-mode" from a notmuch-search view in emacs to see\r
+> what those look like.)\r
+\r
+Exactly, that's what I meant by manually.  Those messages don't match a\r
+nice generic pattern.\r
+\r
+> Meanwhile, just archiving the message won't make things perfect for\r
+> you. The document in the database point to the broken file is still\r
+> there. And it should still have all of its terms, so will likely show up\r
+> if you do more searches. (The "(null)" stuff you're seeing isn't because\r
+> the message is NULL---for example, notmuch was able to find the date,\r
+> etc. It's just that notmuch couldn't find the subject and authors when\r
+> it went to look for the file.)\r
+\r
+Yeah.\r
+\r
+> So if GMail+offlineimap continues to shuffle your files around, you're\r
+> going to keep seeing more and more confusion like this buildup.\r
+> \r
+> So we really just need to teach notmuch how to handle an unstable file\r
+> store in order to be able to use it in this kind of setup.\r
+\r
+This seems unavoidable with maildir in the presence of any\r
+synchronization, or use of a different client.\r
+\r
+An ugly, but possible solution would be to mirror the entire maildir via\r
+hard links with whatever naming scheme you like.  You then have a stable\r
+link to the file and can resolve changing names in the real maildir.\r
+This eats up a lot of inodes.\r
+\r
+Jed\r