unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jeremy Nickurak <not-much@trk.nickurak.ca>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: gmail label support in offlineimap - update
Date: Wed, 28 Nov 2012 09:46:52 -0700	[thread overview]
Message-ID: <CA+eQo_0wOSjHoMK30_PwGZonBNbSDCRy+ghX-TnimfZp++8cBg@mail.gmail.com> (raw)
In-Reply-To: <50B62409.7050706@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 787 bytes --]

As far as syncing flags to notmuch, it sounds like this would be easy to
achieve with an independent 3rd tool, or even a small script:
1) Find files in the maildir modified since the last check
2) Read their keywords headers
3) Update the notmuch tags accordingnly.

The other direction sounds like it would be trickier though, since there's
no obvious way to say "what notmuch tags have changed since time X?". Is
this something that notmuch could provide?

Alternatively, would it be a good idea to give notmuch a tags-changed hook,
so that an external tool could be called on a tag change? That sounds like
would solve this problem, keep the gmail/imap logic safely away from
notmuch, and probably provide some really interesting other opportunities
for automation of things by tags.

[-- Attachment #2: Type: text/html, Size: 888 bytes --]

  parent reply	other threads:[~2012-11-28 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 14:47 gmail label support in offlineimap - update Rainer M Krug
2012-11-28 16:27 ` Peter Portante
2012-11-28 16:46 ` Jeremy Nickurak [this message]
2012-11-28 18:09   ` David Bremner
2012-11-29  8:57     ` Rainer M Krug
2012-11-29 13:33       ` Michal Nazarewicz
2012-11-29 16:09         ` Rainer M Krug
2012-11-28 18:47   ` Michal Nazarewicz
2012-11-29  8:59     ` Rainer M Krug

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=CA+eQo_0wOSjHoMK30_PwGZonBNbSDCRy+ghX-TnimfZp++8cBg@mail.gmail.com \
    --to=not-much@trk.nickurak.ca \
    --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).