From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Categories Date: Mon, 15 Oct 2007 19:57:42 +0100 Message-ID: <87bqb0tdcp.fsf@bzg.ath.cx> References: <1sodf4n1wn.fsf@home.net> <87przk8nom.fsf@bzg.ath.cx> <877ils8jpu.fsf@bzg.ath.cx> <467cec015b737d0c4c69382db9d7f314@science.uva.nl> <87fy0gw9my.fsf@bzg.ath.cx> <87r6jwuuue.fsf@bzg.ath.cx> <877iloust1.fsf@bzg.ath.cx> 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 1IhUCI-0008Os-H1 for emacs-orgmode@gnu.org; Mon, 15 Oct 2007 13:57:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IhUCG-0008Oe-KR for emacs-orgmode@gnu.org; Mon, 15 Oct 2007 13:57:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IhUCG-0008Ob-Fh for emacs-orgmode@gnu.org; Mon, 15 Oct 2007 13:57:44 -0400 Received: from ug-out-1314.google.com ([66.249.92.173]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IhUCF-0002DM-VZ for emacs-orgmode@gnu.org; Mon, 15 Oct 2007 13:57:44 -0400 Received: by ug-out-1314.google.com with SMTP id a2so270991ugf for ; Mon, 15 Oct 2007 10:57:42 -0700 (PDT) In-Reply-To: (Richard G. Riley's message of "Mon, 15 Oct 2007 19:46:42 +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: > Aha ok. Note that like a lot of things its easy when you know how. Well, my post started with this: ,---- | 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) } `---- So you could deduce NEXT wasn't a tag. But I wrongly assumed you knew about combined tags/TODO searches. I agree these are a bit complex, but they are very well documented in the manual and the "Matching tags and properties" section explicitely refers to id (info "(org)Matching tags and properties") > As I said before one of the problems with flexible programs like org > is that sometimes preferred usage doesn't immediately become apparent > to the reader. I don't know if using combined searches in custom agenda views "preferred" and I certainly should have gone more into details here. If you see anything that could clarify the manual for what you were searching, please suggest. -- Bastien