From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: Re: [agenda] skip non-habit SCHEDULED Date: Thu, 19 May 2011 23:12:56 +0200 Message-ID: References: <87wrhm8lk6.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:42669) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNAWg-00049U-U6 for emacs-orgmode@gnu.org; Thu, 19 May 2011 17:12:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QNAWf-0003pW-MH for emacs-orgmode@gnu.org; Thu, 19 May 2011 17:12:58 -0400 Received: from mail-ey0-f169.google.com ([209.85.215.169]:38669) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNAWf-0003pS-Hy for emacs-orgmode@gnu.org; Thu, 19 May 2011 17:12:57 -0400 Received: by eyd9 with SMTP id 9so1199613eyd.0 for ; Thu, 19 May 2011 14:12:56 -0700 (PDT) In-Reply-To: <87wrhm8lk6.fsf@fastmail.fm> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Matt Lundin Cc: Org Mode Hi Matt On Thu, May 19, 2011 at 22:47, Matt Lundin wrote: > Michael Brand 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