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 9FF29431FBC; Sat, 21 Nov 2009 19:53:38 -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 sZRS1VwSJ2+K; Sat, 21 Nov 2009 19:53:38 -0800 (PST) Received: from cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id AE29E431FAE; Sat, 21 Nov 2009 19:53:37 -0800 (PST) From: Carl Worth To: Jed Brown , Jan Janak In-Reply-To: <876393tqfk.fsf@59A2.org> References: <1258630481-5133-1-git-send-email-jan@ryngle.com> <1258630481-5133-2-git-send-email-jan@ryngle.com> <87lji2bmrb.fsf@yoom.home.cworth.org> <87my2f329e.fsf@yoom.home.cworth.org> <876393tqfk.fsf@59A2.org> Date: Sun, 22 Nov 2009 04:53:25 +0100 Message-ID: <87einr2p1m.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: notmuch@notmuchmail.org Subject: Re: [notmuch] [PATCH 2/2] notmuch list: A new command to produce various lists. 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: Sun, 22 Nov 2009 03:53:38 -0000 On Sun, 22 Nov 2009 00:21:19 +0100, Jed Brown wrote: > On Sun, 22 Nov 2009 00:07:57 +0100, Carl Worth wrote: > > One thing we'll still have to think about is how to remove the "virtual > > tags" from the completion list, (once we have virtual tags in the > > configuration file---that is, tags applied automatically based on search > > specifications). > > Do these need to be real tags? Would it be sufficient for them to just > be aliases for search patterns? I think I would prefer the latter > because I could modify the pattern and not have to rewrite tags to the > whole database. Maybe real tags are needed to optimize expensive > patterns, but I wouldn't think the user needs to know about that. They are conceptually just aliases for search patterns, yes. But when I'm working with my mail I think I want them be accessible in an identical way to tags I apply manually. That is I want to be able to search for "tag:foo" and filter the current search view on the "bar" tag without having to remember to distinguish as a users whether "foo" or "bar" is a tag or an "aliased search term". As for your concerns, tag updates are going to be made really fast, (we just *have* to fix that bug, and soon), so I don't think there's going to be any problem with updating these rules and having to update the state in the database. -Carl