From: David Mazieres <dm-list-email-notmuch@scs.stanford.edu>
To: Daniel Schoepe <daniel@schoepe.org>, notmuch@notmuchmail.org
Subject: Re: notmuch-lazysync -- synchronizing tags using dropbox
Date: Tue, 21 Jul 2015 17:16:05 -0700 [thread overview]
Message-ID: <871tg1yrlm.fsf@ta.scs.stanford.edu> (raw)
In-Reply-To: <87a8upjqts.fsf@schoepe.localhost>
Daniel Schoepe <daniel@schoepe.org> writes:
> The way tag changes are logged is a bit of a hack, but it could be
> improved in the future by adding a post-tag hook to notmuch.
One thing to look into, if you are thinking of a better logging
mechanism, is that Xapian itself has a change logging mechanism for
replicating databases (http://xapian.org/docs/replication.html).
I do think it would be cleaner to do this in a way that is integrated
with notmuch, but I think the best way to do this is to integrate a
"modtime" value into the Xapian database. Having a modtime for each
record would not only allow incremental transfers (just record the
highest timestamp sent to each replica), it would also solve this
terrible problem that in emacs you can end up tagging messages you don't
see (because you apply a tag to the query result, when new mail has come
in--which would be solved by tagging only through the higest modtime
actually displayed).
When you have one mechanism (modtime) that solves multiple problems, it
is likely the right thing to use...
David
next prev parent reply other threads:[~2015-07-22 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 18:41 notmuch-lazysync -- synchronizing tags using dropbox Daniel Schoepe
2015-07-22 0:16 ` David Mazieres [this message]
2015-07-22 9:19 ` David Bremner
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=871tg1yrlm.fsf@ta.scs.stanford.edu \
--to=dm-list-email-notmuch@scs.stanford.edu \
--cc=daniel@schoepe.org \
--cc=mazieres-cveh8aunzppx7vn8bfg87dyijs@temporary-address.scs.stanford.edu \
--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).