Hi Matt
On Thu, May 19, 2011 at 22:47, Matt Lundin <[email protected]> wrote:
> Michael Brand <[email protected]> writes:
>> - org-agenda-skip-function: not available for type agenda AFAIK
>
> Good news: the skip function does apply to agenda views.
Thank you for pointing this out and for the example that does exactly
what I asked for. I thought that org-agenda-skip-function is not
available for the type agenda from checking the doc. Could the doc be
changed by adding @code {agenda} like this?:
----------------------------------------
diff --git a/doc/org.texi b/doc/org.texi
index aa34cd3..6b469cc 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -14376,12 +14376,12 @@ other block) with @code{org-narrow-to-block}.
@vindex org-agenda-skip-function
@vindex org-agenda-skip-function-global
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. You can specify a global
-condition that will be applied to all agenda views, this condition would be
-stored in the variable @code{org-agenda-skip-function-global}. More
+made by these agenda views: @code{agenda}, @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. You can specify a
+global condition that will be applied to all agenda views, this condition
+would be stored in the variable @code{org-agenda-skip-function-global}. More
commonly, such a definition is applied only to specific custom searches,
using @code{org-agenda-skip-function}.
----------------------------------------
Michael
