emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Carsten Dominik <carsten@orgmode.org>,
	emacs-orgmode@gnu.org, jeff stern <jas@uci.edu>
Subject: Re: Confusion about tags-todo matches and TODO keywords
Date: Tue, 22 Jun 2010 14:47:59 +0200	[thread overview]
Message-ID: <513B57FB-B126-4E77-B403-B1A5C3E051E3@gmail.com> (raw)
In-Reply-To: <87vd9bfgxr.fsf@gollum.intra.norang.ca>

Applied, thanks!

- Carsten

On Jun 22, 2010, at 1:24 PM, Bernt Hansen wrote:

> Carsten Dominik <carsten.dominik@gmail.com> 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

      reply	other threads:[~2010-06-22 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 23:39 Confusion about tags-todo matches and TODO keywords Bernt Hansen
2010-06-22  8:51 ` Carsten Dominik
2010-06-22 11:24   ` Bernt Hansen
2010-06-22 12:47     ` Carsten Dominik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=513B57FB-B126-4E77-B403-B1A5C3E051E3@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bernt@norang.ca \
    --cc=carsten@orgmode.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jas@uci.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).