Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id A988E431FBF for ; Tue, 22 Apr 2014 15:07:17 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled 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 nLRUXhT8C8EM for ; Tue, 22 Apr 2014 15:07:10 -0700 (PDT) Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net [87.98.215.224]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 8BF65431FBD for ; Tue, 22 Apr 2014 15:07:10 -0700 (PDT) Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim 4.72) (envelope-from ) id 1Wcioa-0007Fv-NO; Tue, 22 Apr 2014 22:05:20 +0000 Received: (nullmailer pid 19601 invoked by uid 1000); Tue, 22 Apr 2014 22:05:02 -0000 From: David Bremner To: Gaute Hope Subject: Re: [PATCH] Add configurable changed tag to messages that have been changed on disk In-Reply-To: <1397163239-sup-5101@qwerzila> References: <1396800683-9164-1-git-send-email-eg@gaute.vetsj.com> <87wqf2gqig.fsf@ta.scs.stanford.edu> <1397140962-sup-6514@qwerzila> <87wqexnqvb.fsf@ta.scs.stanford.edu> <1397163239-sup-5101@qwerzila> User-Agent: Notmuch/0.18~rc0 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Wed, 23 Apr 2014 07:05:02 +0900 Message-ID: <87d2g9ja0h.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain Cc: notmuch 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: Tue, 22 Apr 2014 22:07:17 -0000 Gaute Hope writes: > > I am talking about syncing tags to a maildir _folder_, not flags. It > could be implemented as maildir.synchronize is now, but it would be a > larger feature which could work in a lot of different ways. > So to try and clarify the use case, this could be used to add a tag "changed" to each message-id that had one or more files moved/added/deleted on disk. You would then retag that message using something like the output of notmuch search --output=files so that a set of tags corresponds to a set of folders containing the message. Is this correct? I guess the proposed ctime information could be used for this as well, if it also tracked those non-tag related changes. I guess this would make it worse for David M's purposes (although presumeably still better than nothing). d