From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manish Subject: Re: Showing scheduled blocked tasks [SEC=UNCLASSIFIED] Date: Mon, 15 Mar 2010 21:56:00 +0530 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NrD7Y-0006w0-8l for emacs-orgmode@gnu.org; Mon, 15 Mar 2010 12:26:24 -0400 Received: from [140.186.70.92] (port=50798 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NrD7W-0006vp-TD for emacs-orgmode@gnu.org; Mon, 15 Mar 2010 12:26:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NrD7V-00041n-Dz for emacs-orgmode@gnu.org; Mon, 15 Mar 2010 12:26:22 -0400 Received: from mail-iw0-f175.google.com ([209.85.223.175]:62195) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NrD7V-00041Z-BC for emacs-orgmode@gnu.org; Mon, 15 Mar 2010 12:26:21 -0400 Received: by iwn5 with SMTP id 5so150160iwn.24 for ; Mon, 15 Mar 2010 09:26:20 -0700 (PDT) In-Reply-To: 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: Matthew Phillips Cc: Matthew Phillips , emacs-orgmode@gnu.org On Thu, Mar 11, 2010 at 7:04 AM, Matthew Phillips wrote: > Hello all, > > I am trying to get a TODO tags view in my daily agenda just shows > the first TODO of a =93Project=94 (a la the =93next action=94 in GTD). > This allows me to have a TODO =93tags=94 block in my custom agenda > that doesn=92t run to several pages: I just see the next action for > each project, and, as each action is marked DONE, the next one > pops up. have you considered using org-depend? this is what i use for almost exactly what you described: 1. a project has several TODOs 2. the first TODO (manually) is assigned a TRIGGER property with "chain-siblings(NEXT)" as value 3. as this task is marked DONE, the one below is switched to NEXT state and also gets the property 4. switching to NEXT causes org-todo-state-tags-triggers to tag the task with NEXT tag 5. a custom agenda view adds a block of these NEXT tasks hth --=20 manish