From: Jed Brown <jed@59A2.org>
To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
Subject: Re: Asynchronous tagging
Date: Sat, 21 Nov 2009 22:17:34 +0100 [thread overview]
Message-ID: <87aayftw5t.fsf@59A2.org> (raw)
In-Reply-To: <87tywn386a.fsf@yoom.home.cworth.org>
On Sat, 21 Nov 2009 22:00:13 +0100, Carl Worth <cworth@cworth.org> wrote:
> Ah, OK. So you made a change on the Gmail side and that caused a file to
> be renamed locally.
yes
> Or did you mean you removed the tag from within emacs? In that case, the
> search term used to find the message is the message id itself. (Try
> running "M-x visible-mode" from a notmuch-search view in emacs to see
> what those look like.)
Exactly, that's what I meant by manually. Those messages don't match a
nice generic pattern.
> Meanwhile, just archiving the message won't make things perfect for
> you. The document in the database point to the broken file is still
> there. And it should still have all of its terms, so will likely show up
> if you do more searches. (The "(null)" stuff you're seeing isn't because
> the message is NULL---for example, notmuch was able to find the date,
> etc. It's just that notmuch couldn't find the subject and authors when
> it went to look for the file.)
Yeah.
> So if GMail+offlineimap continues to shuffle your files around, you're
> going to keep seeing more and more confusion like this buildup.
>
> So we really just need to teach notmuch how to handle an unstable file
> store in order to be able to use it in this kind of setup.
This seems unavoidable with maildir in the presence of any
synchronization, or use of a different client.
An ugly, but possible solution would be to mirror the entire maildir via
hard links with whatever naming scheme you like. You then have a stable
link to the file and can resolve changing names in the real maildir.
This eats up a lot of inodes.
Jed
next prev parent reply other threads:[~2009-11-21 21:17 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 [this message]
2009-11-21 20:01 ` Carl Worth
2009-11-21 20:43 ` Karl Wiberg
2009-11-21 20:48 ` Jed Brown
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=87aayftw5t.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).