From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Confusion about tags-todo matches and TODO keywords Date: Tue, 22 Jun 2010 14:47:59 +0200 Message-ID: <513B57FB-B126-4E77-B403-B1A5C3E051E3@gmail.com> References: <87fx0ggdl1.fsf@gollum.intra.norang.ca> <9485A6F0-9345-4A44-BA8B-0751E6060991@gmail.com> <87vd9bfgxr.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=34382 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OR3J7-0002IG-K4 for emacs-orgmode@gnu.org; Tue, 22 Jun 2010 09:14:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OR3J6-0006Ot-9M for emacs-orgmode@gnu.org; Tue, 22 Jun 2010 09:14:29 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:56799) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OR3J6-0006Nt-5J for emacs-orgmode@gnu.org; Tue, 22 Jun 2010 09:14:28 -0400 Received: by wyf28 with SMTP id 28so3764677wyf.0 for ; Tue, 22 Jun 2010 06:14:24 -0700 (PDT) In-Reply-To: <87vd9bfgxr.fsf@gollum.intra.norang.ca> 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: Bernt Hansen Cc: Carsten Dominik , emacs-orgmode@gnu.org, jeff stern Applied, thanks! - Carsten On Jun 22, 2010, at 1:24 PM, Bernt Hansen wrote: > Carsten Dominik writes: > >> Hi Bernt, >> >> On Jun 22, 2010, at 1:39 AM, Bernt Hansen wrote: >> >>> I still think 'TODO keyword' matches any todo keyword defined in >>> org-todo-keywords and maybe I need to be re-educated :) >> >> Indeed, "TODO" is used in two different ways in the documentation. >> When I talk about the TODO sparse tree, about the global TODO list >> (C- >> c a t), and the tags-TODO match, >> this means not-done TODO items. >> >> However, the phrase TODO keyword certainly includes DONE states. I >> think we should keep it like this, and I will add the not-done in a >> couple of places where it makes sense. >> >> Here is a patch I am proposing for this. Please take a look if >> this would be sufficient to clarify the issue. >> > > Hi Carsten. > > The patch you sent was whitespace damaged so I couldn't apply it to my > repository. Reading through the changes I think this helps a lot to > clarify things. > > The only additional change I can think of that would be useful would > be > to explicitly state that using the agenda tags-todo or a tags search > with /! will only match not-done TODO keywords. > > Maybe something like this? > > (This adds one sentence before "Examples:" and reformats the > paragraph) > > > --8<---------------cut here---------------start------------->8--- > diff --git a/doc/org.texi b/doc/org.texi > index 17615e0..550394d 100644 > --- a/doc/org.texi > +++ b/doc/org.texi > @@ -7009,12 +7009,13 @@ different way to test TODO states in a > search. For this, terminate the > tags/property part of the search string (which may include several > terms > connected with @samp{|}) with a @samp{/} and then specify a Boolean > expression just for TODO keywords. The syntax is then similar to > that for > -tags, but should be applied with care: for example, a positive > -selection on several TODO keywords cannot meaningfully be combined > with > -boolean AND. However, @emph{negative selection} combined with AND > can be > -meaningful. To make sure that only lines are checked that actually > have any > -TODO keyword (resulting in a speed-up), use @kbd{C-c a M}, or > equivalently > -start the TODO part after the slash with @samp{!}. Examples: > +tags, but should be applied with care: for example, a positive > selection on > +several TODO keywords cannot meaningfully be combined with boolean > AND. > +However, @emph{negative selection} combined with AND can be > meaningful. To > +make sure that only lines are checked that actually have any TODO > keyword > +(resulting in a speed-up), use @kbd{C-c a M}, or equivalently start > the TODO > +part after the slash with @samp{!}. Using @kbd{C-c a M} or > @samp{/!} will > +not match TODO keywords in a DONE state. Examples: > > @table @samp > @item work/WAITING > --8<---------------cut here---------------end--------------->8--- > > > Thanks, > Bernt > - Carsten