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 412BF431FBC for ; Tue, 24 Nov 2009 09:51:22 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org 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 5DP3ygFiPSgi for ; Tue, 24 Nov 2009 09:51:18 -0800 (PST) Received: from mail-ew0-f220.google.com (mail-ew0-f220.google.com [209.85.219.220]) by olra.theworths.org (Postfix) with ESMTP id ABCA1431FAE for ; Tue, 24 Nov 2009 09:51:18 -0800 (PST) Received: by ewy20 with SMTP id 20so3194614ewy.0 for ; Tue, 24 Nov 2009 09:51:17 -0800 (PST) Received: by 10.213.23.80 with SMTP id q16mr5503093ebb.3.1259085077282; Tue, 24 Nov 2009 09:51:17 -0800 (PST) Received: from x61s.janakj ([213.192.30.141]) by mx.google.com with ESMTPS id 23sm2798515eya.35.2009.11.24.09.51.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 24 Nov 2009 09:51:15 -0800 (PST) Received: by x61s.janakj (Postfix, from userid 1000) id 8F718440651; Tue, 24 Nov 2009 18:51:03 +0100 (CET) Date: Tue, 24 Nov 2009 18:51:03 +0100 From: Jan Janak To: Keith Packard Message-ID: <20091124175103.GG7669@ryngle.com> References: <87639122sx.fsf@yoom.home.cworth.org> <87bpismx21.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: notmuch@notmuchmail.org Subject: Re: [notmuch] notmuch 'index' mode. X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.12 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, 24 Nov 2009 17:51:22 -0000 On 24-11 08:38, Keith Packard wrote: > On Tue, 24 Nov 2009 13:14:07 +0100, Jan Janak wrote: > > > I like this. I think this is much cleaner than the "virtual tag" > > approach. > > A disadvantage I see is that you would not see this 'virtual tags' in > the list of tags on each message. Maybe I don't understand how virtual tags are really supposed to work. I thought that the term "virtual tags" is just another name for "named" search terms and it is named "virtual tags" because they can actually be attached to messages stored in the database. And if I remember it correctly, Carl said somewhere that virtual tags will be added/removed automatically to messages if the corresponding search term gets changed. If my understanding is correct, then we won't be able to show virtual tags along with "normal" tags anyway. We would probably need a separate list just for virtual tags. One of the reasons is that you can add and remove normal tags to messages manually, but you cannot easily do the same with virtual tags. If you remove a virtual tag from a message and then update the search term bound to that virtual tag, as soon as you change the search term, the virtual tag might be added to the message again if the new search expression still matches the message. Unlike real tags, the user won't be able to add and remove virtual tags to messages arbitrarily without the risk that notmuch changes the selection behind his back on the next update of the configuration file (assuming that the search expression is stored in the configuration file). We would probably need to make sure that the user knows which tags are virtual and which are real and that means notmuch would have to present them differently, possibly in a separate list. Thinking more about this, we could probably make it possible to add and remove virtual tags to messages manually by storing the information about what the user did with the virtual tag along with the message (i.e. this virtual tag is pinned to the message so don't remove it when the search term is changed). Maybe I just don't understand how virtual tags are really supposed to work, but it seems to me as a can of worms just waiting to be opened :-). -- Jan