From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Todo item property search Date: Fri, 03 Sep 2010 10:19:55 +0200 Message-ID: <87r5hbxmqc.fsf@gnu.org> References: <38124.40111.qm@web29612.mail.ird.yahoo.com> <87occfzr0r.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=43448 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OrRV6-0002ri-87 for emacs-orgmode@gnu.org; Fri, 03 Sep 2010 04:19:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OrRV4-0003lG-Td for emacs-orgmode@gnu.org; Fri, 03 Sep 2010 04:19:56 -0400 Received: from mail-ww0-f49.google.com ([74.125.82.49]:51518) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OrRV4-0003l5-Pf for emacs-orgmode@gnu.org; Fri, 03 Sep 2010 04:19:54 -0400 Received: by wwb24 with SMTP id 24so1886104wwb.30 for ; Fri, 03 Sep 2010 01:19:53 -0700 (PDT) In-Reply-To: (Carsten Dominik's message of "Fri, 3 Sep 2010 07:02:39 +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: Carsten Dominik Cc: Chevalier Julien , emacs-orgmode@gnu.org Carsten Dominik writes: > Hi Bastien, the todo tree does not use the tags scanner, so the > skipper is completely ignored here. Okay, thanks for the precision. Here is a patch that makes it clear in the manual. Shall I apply it? diff --git a/doc/org.texi b/doc/org.texi index 4ce32ce..71d1823 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -13781,10 +13781,11 @@ written in a way such that it does nothing in buffers that are not in @section Special agenda views @cindex agenda views, user-defined -Org provides a special hook that can be used to narrow down the -selection made by any of the agenda views. You may specify a function -that is used at each match to verify if the match should indeed be part -of the agenda view, and if not, how much should be skipped. +Org provides a special hook that can be used to narrow down the selection +made by these agenda views: @code{todo}, @code{alltodo}, @code{tags}, @code{tags-todo}, +@code{tags-tree}. You may specify a function that is used at each match to verify +if the match should indeed be part of the agenda view, and if not, how +much should be skipped. Let's say you want to produce a list of projects that contain a WAITING tag anywhere in the project tree. Let's further assume that you have -- Bastien