From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tim O'Callaghan" Subject: Re: property searches for #+CATEGORY Date: Wed, 7 Nov 2007 15:52:55 +0100 Message-ID: <3d6808890711070652l68d51190y2b4b735543cded7c@mail.gmail.com> References: <20071107111730.GH13544@atlantic.linksys.moosehall> <3d6808890711070523u50bd8bbp963960978171e132@mail.gmail.com> <20071107133404.GL13544@atlantic.linksys.moosehall> <3d6808890711070559x3b24ed3djc4276fdc09d074a9@mail.gmail.com> <20071107142805.GN13544@atlantic.linksys.moosehall> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IpmHB-0001sS-Or for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 09:53:05 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IpmHA-0001qW-9h for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 09:53:05 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpmHA-0001qI-4y for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 09:53:04 -0500 Received: from nf-out-0910.google.com ([64.233.182.189]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IpmH9-0008Sc-L4 for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 09:53:03 -0500 Received: by nf-out-0910.google.com with SMTP id f5so2339747nfh for ; Wed, 07 Nov 2007 06:52:55 -0800 (PST) In-Reply-To: <20071107142805.GN13544@atlantic.linksys.moosehall> Content-Disposition: inline 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: Adam Spiers , org-mode mailing list On 07/11/2007, Adam Spiers wrote: > On Wed, Nov 07, 2007 at 02:59:35PM +0100, Tim O'Callaghan wrote: > > On 07/11/2007, Adam Spiers wrote: > > > On Wed, Nov 07, 2007 at 02:23:12PM +0100, Tim O'Callaghan wrote: > > > > It would seem to me that this is exactly what tags does. > > > > You could move everything down a level and use tag inheritance: > > > > * personal stuff :personal: > > > > * work stuff :work: > > > > > > I could, but this would mean that each file would have a single > > > top-level entry, and the entire contents would be indented an extra > > > level, which I fear is a rather unattractive solution! > > > > It's the technique i've been using, and yes, it is unattractive. > > > > When i thought of tags, it was not explicitly for GTD context > > specifier, it was also for adding searchable metadata to a todo node. > > Same here. I used tags for a lot more than GTD contexts, e.g. also > for a rough ETC and to group them by areas of responsibility. > (N.B. Sometimes a task can be motivated by multiple areas of > responsibility, so subheadings aren't good enough.) > > > How about adding the context to the tag table with a prefix character, say #? > > I don't follow you, sorry. Perhaps I should state explicitly that my > need to distinguish between 'work' and 'personal' categories has > nothing to do with my use of GTD contexts. I can (and do very often) > work from home, and I also occasionally(!) do personal tasks from the > office. > My point with the taxonomy is that Categories especially 'personal' and 'work' can be thought of as Meta Contexts (i wanted to say Meta-TAGS, but that might get confusing). So contexts that are arbitrary but are used to group many actual physical contexts (TAGS) of todo nodes. The '#' was the thought that if you treat Categories as a type of tag, then you could add them to the tag search mechanism. To avoid collision, such as work - the physical context and work, the category, prefix them with a meta-character such as # which cannot normally be in a tag name. So a categorised tag-todo search might be: "#work+work+email/TODO" Tim.