From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: automatic scheduling of next task in project Date: Thu, 06 Mar 2014 08:13:02 -0600 Message-ID: <87zjl3za8h.fsf@fastmail.fm> References: <21263.7097.839300.475663@raynernix2.earthsci.unimelb.edu.au> <2014-03-06T14-11-29@devnull.Karl-Voit.at> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56397) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLZ2s-0003Xr-9K for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 09:13:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WLZ2n-0005J5-62 for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 09:13:10 -0500 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:58265) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLZ2m-0005J1-UX for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 09:13:05 -0500 In-Reply-To: <2014-03-06T14-11-29@devnull.Karl-Voit.at> (Karl Voit's message of "Thu, 6 Mar 2014 14:15:09 +0100") 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: Karl Voit Cc: news1142@Karl-Voit.at, emacs-orgmode@gnu.org Karl Voit writes: > * Peter Rayner wrote: >> I would like org-mode to remind me automatically of the next task in a >> project. Perhaps an example will help. I'll use outline headings to >> show the levels of tasks > > Auto-scheduling might be difficult. > > In my workflows I am using dependencies with :BLOCKER: and settings > SCHEDULED dates roughly but on the aggressive side. > > With (setq org-agenda-dim-blocked-tasks t) I get them all on my > agenda. You just have to learn to visually ignore the dimmed tasks. > From time to time I re-check dimmed tasks for the reason why they > are dimmed/blocked to find dead-ends. You can also set org-agenda-dim-blocked-tasks to 'invisible, which will remove blocked tasks entirely from the agenda. Then, you could add the property ":ORDERED: t" to the heading and schedule them (for the diary agenda) or mark them NEXT/TODO (for the todo list). This would cause each event to appear on the agenda after the blocking task is marked done. > An additional/other approach would be the use of :TRIGGER: > chain-siblings(NEXT) in order to move the NEXT state from a finished > task to the next one. Or, since the OP is using org-depend.el (in contrib), he could also use :TRIGGER: chain-siblings-scheduled(NEXT). Best, Matt