From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Categories Date: Fri, 12 Oct 2007 18:00:37 +0100 Message-ID: <87fy0gw9my.fsf@bzg.ath.cx> References: <1sodf4n1wn.fsf@home.net> <87przk8nom.fsf@bzg.ath.cx> <877ils8jpu.fsf@bzg.ath.cx> <467cec015b737d0c4c69382db9d7f314@science.uva.nl> 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 1IgMwQ-0003SL-Ke for emacs-orgmode@gnu.org; Fri, 12 Oct 2007 12:00:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IgMwP-0003S6-5E for emacs-orgmode@gnu.org; Fri, 12 Oct 2007 12:00:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IgMwP-0003S3-0Q for emacs-orgmode@gnu.org; Fri, 12 Oct 2007 12:00:45 -0400 Received: from nf-out-0910.google.com ([64.233.182.190]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IgMwN-0000pM-Na for emacs-orgmode@gnu.org; Fri, 12 Oct 2007 12:00:44 -0400 Received: by nf-out-0910.google.com with SMTP id f5so840883nfh for ; Fri, 12 Oct 2007 09:00:38 -0700 (PDT) In-Reply-To: (Richard G. Riley's message of "Fri, 12 Oct 2007 17:04:00 +0200") 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 Richard G Riley writes: > Completion doesnt work for me. Possibly this is a result of using > icicles? You just TAB to completion? Can you please provide more details: What version of Org-mode? What did you do? What did you expect? What did you get instead? > This might seem like an incredibly naive question, but with the > concept of "general properties", where do TAGs fit in now? TAGs are special properties. They are special regarding the way you access them (C-c C-c), the way you display them (flushright) and the way Org can process them (with specific search/sort queries.) But in other respect, they are just "properties" of an entry. Hope this might help you find the best use for tags. > I am having difficulty seeing the best way to utilise the tools and > would appreciate some wise words of guidance here. For me a todo line gets associated with : | a project | CATEGORY | | a process state | TODO keyword | | an action-type | tags | | a context of action | tags | My setting for tags is this: #+TAGS: { Read(r) Write(w) Code(c) } #+TAGS: Mail(m) Print(p) #+TAGS: { @HOME(H) @LAB(L) } #+TAGS: { @Online(O) @Offline(F) } The first two lines are action-types. The two last lines are contexts. The conventions I use are these: 1) the keys for action-types are lower-case, the keys for contexts are upper-case. 2) contexts comes with a leading "@" 3) the tags for *physical* contexts are all capitalized, while those for notional contexts are just first-letter capitalized. The tags that I'm more likely to use are Read, Write or Code. A subset of my agenda views: (setq org-agenda-custom-commands '(("r" tags-todo "Read/NEXT" nil) ("w" tags-todo "Write/NEXT" nil) ("R" tags-todo "Read/NEXT|TODO" nil) ("W" tags-todo "Write/NEXT|INPROGRESS" nil))) Then I regularily check for something to read with "r" (meaning something to read next) or "R" (including other TODO); or I check for things that I have to write with "w" (the things I have to write next) or "W" (including work in progress, which is likely to take more than on day.) For the "Mail" an "Print" tags, i use the normal C-c a m key, since I don't use them that often. At the beginning I worried too much about having a consistent set of tags. For the example above, there is some overlap between Mail Write and Code. But you don't need to worry about that. Just use the tags, and progressively you will be able to get rid of useless one. HTH, -- Bastien