From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 03CEC431FC0 for ; Mon, 25 Jan 2010 08:22:11 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] autolearn=ham Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8UeDVcuooeTo for ; Mon, 25 Jan 2010 08:22:10 -0800 (PST) Received: from mout-xforward.perfora.net (mout-xforward.perfora.net [74.208.4.202]) by olra.theworths.org (Postfix) with ESMTP id 57EA4431FBC for ; Mon, 25 Jan 2010 08:22:10 -0800 (PST) Received-SPF: softfail (mxus0: transitioning domain of pioto.org does not designate 207.192.69.249 as permitted sender) client-ip=207.192.69.249; envelope-from=pioto@pioto.org; helo=everglades.pioto.org; Received: from everglades.pioto.org (everglades.pioto.org [207.192.69.249]) by mx.perfora.net (node=mxus0) with ESMTP (Nemesis) id 0MPEJU-1NV3yq3yHQ-0058fE for notmuch@notmuchmail.org; Mon, 25 Jan 2010 11:22:09 -0500 Received: from aether.pioto.org (unknown [72.95.222.13]) (Authenticated sender: pioto) by everglades.pioto.org (Postfix) with ESMTPA id 7912616008C; Mon, 25 Jan 2010 11:22:07 -0500 (EST) Received: by aether.pioto.org (Postfix, from userid 1000) id 85F0F66FA8; Mon, 25 Jan 2010 11:22:47 -0500 (EST) From: Mike Kelly To: Sebastian Spaeth , martin f krafft , Asheesh Laroia In-Reply-To: <87k4v670s3.fsf@SSpaeth.de> References: <20100111221909.GA30299@lapse.rw.madduck.net> <1263267603-sup-302@elise> <20100112045152.GA15275@lapse.rw.madduck.net> <20100114203730.GE4691@lapse.rw.madduck.net> <20100125004659.GA24818@lapse.rw.madduck.net> <87k4v670s3.fsf@SSpaeth.de> Message-Id: <20100125162247.85F0F66FA8@aether.pioto.org> Date: Mon, 25 Jan 2010 11:22:47 -0500 (EST) Cc: notmuch Subject: Re: Git as notmuch object store (was: Potential problem using Git for mail) X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 16:22:11 -0000 On Mon, 25 Jan 2010 14:49:00 +0100, "Sebastian Spaeth" wrote: > > On Mon, 25 Jan 2010 13:46:59 +1300, martin f krafft 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