From: Mike Kelly <pioto@pioto.org>
To: Sebastian Spaeth <Sebastian@SSpaeth.de>,
martin f krafft <madduck@madduck.net>,
Asheesh Laroia <asheesh@asheesh.org>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: Git as notmuch object store (was: Potential problem using Git for mail)
Date: Mon, 25 Jan 2010 11:22:47 -0500 (EST) [thread overview]
Message-ID: <20100125162247.85F0F66FA8@aether.pioto.org> (raw)
In-Reply-To: <87k4v670s3.fsf@SSpaeth.de>
On Mon, 25 Jan 2010 14:49:00 +0100, "Sebastian Spaeth" <Sebastian@SSpaeth.de> wrote:
>
> On Mon, 25 Jan 2010 13:46:59 +1300, martin f krafft <madduck@madduck.net> wrote:
> > I think we all kinda agreed that the Maildir flags should not be
> > used by notmuch and that things like Sebastian's notmuchsync should
> > be used if people wanted flags represented in Maildir filenames.
>
> While notmuchsync fullfils my needs, it is a kludge. It needs to call
> "notmuch" for each mail where a MailDir flag has changed (which can be
> quite often on an initial run, where most mails are likely to be read),
> this can take a long, long time. It would makes sense IMHO to at least
> pick pioto's "don't set unread if 'S' flag is set" on notmuch new[1].
notmuchsync, as currently implemented, suffers from major performance
issues, in my opinion. It's a useful short term workaround, but not a
good long term solution.
But, I personally will always be using both notmuch and some other IMAP
client (my phone). I want the two to remain in sync easily enough.
notmuch is already much more robust with respect to that than sup, I
think (in terms of handling renames without barfing, etc).
At the very least, I want `notmuch new` to be able to:
If it sees a rename that involves changing maildir flags, alter the
related tags as necessary.
Similarly, provide a mechanism for correlating the folder name with
some set of tags, and change those tags as messages are moved around.
For example, I might have:
~/.notmuch-config:
[database]
path=/home/pioto/mail
...
[tags]
pioto@pioto.org/INBOX.ListMail.notmuch = notmuch
So, a 'tags' section, where each key is the folder name, relative to the
db path, and the value is one or more tag names
This means that I could relabel a message in gmail, for example, and
have the changes apply to notmuch at my next offlineimap run. And, it
means that my existing procmail rules will still be useful both to
notmuch, and to my phone, for the purpose of categorizing things.
I agree that all this should be optional. But, since it is likely the
behavior most people would expect, I think it should be the default.
PS. You mean the 'new-unread' branch, not the 'noarg-count' branch, from
my repo.
--
Mike Kelly
next prev parent reply other threads:[~2010-01-25 16:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 22:19 Idea for storing tags martin f krafft
2010-01-12 3:44 ` Scott Robinson
2010-01-12 4:06 ` martin f krafft
2010-01-12 4:51 ` Potential problem using Git for mail (was: Idea for storing tags) martin f krafft
2010-01-12 19:38 ` Jameson Rollins
2010-01-12 19:55 ` martin f krafft
2010-01-14 8:12 ` Asheesh Laroia
2010-01-14 20:37 ` martin f krafft
2010-01-21 6:28 ` Asheesh Laroia
2010-01-25 0:46 ` Git as notmuch object store (was: Potential problem using Git for mail) martin f krafft
2010-01-25 5:19 ` Asheesh Laroia
2010-01-25 7:43 ` martin f krafft
2010-01-25 13:49 ` Sebastian Spaeth
2010-01-25 16:22 ` Mike Kelly [this message]
2010-01-25 21:46 ` tag dir proposal [was: Re: Git as notmuch object store] Jameson Rollins
2010-01-26 16:32 ` Scott Robinson
2010-01-26 17:03 ` Jameson Rollins
2010-01-28 5:12 ` martin f krafft
2010-01-28 5:28 ` James Westby
2010-01-28 5:34 ` martin f krafft
2010-01-28 6:22 ` James Westby
2010-01-28 9:55 ` martin f krafft
2010-01-28 5:10 ` martin f krafft
2010-01-28 12:32 ` Servilio Afre Puentes
2010-01-28 20:39 ` martin f krafft
2010-01-28 20:49 ` Ben Gamari
2010-01-28 21:11 ` martin f krafft
[not found] ` <1264713802-sup-620@ben-laptop>
[not found] ` <20100128221735.GE8942@lapse.rw.madduck.net>
2010-01-28 23:30 ` Ben Gamari
2010-01-28 21:16 ` Jed Brown
2010-01-25 19:49 ` Git as notmuch object store (was: Potential problem using Git for mail) martin f krafft
2010-01-27 9:00 ` Sebastian Spaeth
2010-02-15 0:51 ` Stewart Smith
2010-01-12 4:11 ` Idea for storing tags Scott Morrison
2010-01-13 1:24 ` martin f krafft
2010-01-13 5:39 ` Scott Morrison
2010-01-13 5:52 ` martin f krafft
2010-01-14 1:37 ` Carl Worth
2010-01-12 21:39 ` David A. Harding
2010-01-14 1:32 ` Carl Worth
2010-01-14 8:04 ` martin f krafft
2010-01-14 22:24 ` Carl Worth
2010-01-14 22:32 ` martin f krafft
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=20100125162247.85F0F66FA8@aether.pioto.org \
--to=pioto@pioto.org \
--cc=Sebastian@SSpaeth.de \
--cc=asheesh@asheesh.org \
--cc=madduck@madduck.net \
--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).