From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: Re: property searches for #+CATEGORY Date: Thu, 8 Nov 2007 00:04:44 +0000 Message-ID: <20071108000444.GA29744@atlantic.linksys.moosehall> References: <20071107111730.GH13544@atlantic.linksys.moosehall> <871wb2p2f9.fsf@bzg.ath.cx> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IputA-0003oe-EW for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 19:04:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Iput8-0003oS-Gz for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 19:04:51 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iput8-0003oP-CN for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 19:04:50 -0500 Received: from mail.beimborn.com ([70.84.38.100]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Iput7-0001Qj-Ij for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 19:04:49 -0500 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id lA804lAZ017331 for ; Wed, 7 Nov 2007 18:04:47 -0600 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id lA804lXx017325 for emacs-orgmode@gnu.org; Thu, 8 Nov 2007 00:04:47 GMT Content-Disposition: inline In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org On Wed, Nov 07, 2007 at 05:20:32PM +0100, Carsten Dominik wrote: > The idea to have groups of agenda files has come up before. > It is hard to implement because agenda creating commands > are *global* commands, so the group should not be a property > of the location from where you call the agenda. > > You can, of course, already make custom commands that are > restricted to a specific group of files, by setting > `org-agenda-files' as one of the options for a custom command > in org-agenda-custom-comands.... Ah! Now that's a nice trick - I hadn't realised you could override variables like that. And given that option values are lisp expressions, one could easily define a group of agenda files via (defvar my-org-personal-agenda-files) and then use that variable in one or more custom agenda commands. Wouldn't that be good enough for most people who want a file-grouping mechanism? (I should make it clear that I still believe it's worth making the tweak we agreed on to support CATEGORY="..." searches which catch #+CATEGORY values.)