From: Jed Brown <jed@59A2.org>
To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
Subject: Re: Asynchronous tagging
Date: Sat, 21 Nov 2009 21:48:19 +0100 [thread overview]
Message-ID: <87d43btxik.fsf@59A2.org> (raw)
In-Reply-To: <874oon4pgv.fsf@yoom.home.cworth.org>
On Sat, 21 Nov 2009 21:01:20 +0100, Carl Worth <cworth@cworth.org> wrote:
> Yes, this is a known bug in Xapian (it rewrites all of the indexed terms
> for the email message even though you're just trying to add/remove one
> term). The Xapian ticket for this is here:
>
> replace_document should make minimal changes to database file
> http://trac.xapian.org/ticket/250
This bug report is concerned that it could require an API change, it
sounds like you think this is unnecessary. Thanks for the detailed
explanation.
> Chris Wilson just contributed a patch to enable read-only usage of
> notmuch while another notmuch process holds the write lock.
I'm running it.
> Does offlineimap use tmp while it's delivering message and then move
> things to new? If so, then maybe all we need to do to fix notmuch to not
> look into tmp directories?
Yes, that's how maildir is supposed to work. Deliver to tmp, hard link
from new, then unlink in tmp. The client should never look in tmp.
Should be very quick to fix in notmuch.
Jed
next prev parent reply other threads:[~2009-11-21 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 18:35 Asynchronous tagging Jed Brown
2009-11-21 19:45 ` Jed Brown
2009-11-21 21:00 ` Carl Worth
2009-11-21 21:17 ` Jed Brown
2009-11-21 20:01 ` Carl Worth
2009-11-21 20:43 ` Karl Wiberg
2009-11-21 20:48 ` Jed Brown [this message]
2009-11-21 20:50 ` Jan Janak
2009-11-21 21:04 ` Jed Brown
2009-11-21 21:15 ` Jan Janak
2009-11-21 22:46 ` Carl Worth
2009-11-22 0:16 ` Keith Packard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d43btxik.fsf@59A2.org \
--to=jed@59a2.org \
--cc=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).