From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: property searches for #+CATEGORY Date: Wed, 7 Nov 2007 17:20:32 +0100 Message-ID: References: <20071107111730.GH13544@atlantic.linksys.moosehall> <871wb2p2f9.fsf@bzg.ath.cx> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Iposw-0003P9-If for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 12:40:14 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ipost-0003Ji-9B for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 12:40:13 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iposs-0003Iw-Pv for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 12:40:10 -0500 Received: from fk-out-0910.google.com ([209.85.128.186]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Iposs-0004BY-ON for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 12:40:11 -0500 Received: by fk-out-0910.google.com with SMTP id 19so4580907fkr for ; Wed, 07 Nov 2007 09:40:09 -0800 (PST) In-Reply-To: <871wb2p2f9.fsf@bzg.ath.cx> 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: Bastien Cc: org-mode mailing list On 7Nov2007, at 3:15 PM, Bastien wrote: > > I understand now. > > I think it would be clearer to distinguish between categorizing files > and categorizing tasks. In a sense, using #+CATEGORY across several > files (as you do) is more a way to group these files under the same > ombrella (conveniently called "category"), rather than to group all > tasks below each #+CATEGORY in the same category. > > Let me say it with other words: if several files share the same > #+CATEGORY, then this bit of information won't be of any help to > distinguish between these files' tasks, it will only help separating > files with #+CATEGORY: A from files with #+CATEGORY: B. > > Then I think the right solution would be to have groups of agenda > files. > Something like: > > #+AGENDA_GROUP: personal 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.... - Carsten