From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xebar Saram Subject: Re: automatic scheduling of next task in project Date: Fri, 7 Mar 2014 10:42:02 +0200 Message-ID: References: <21263.7097.839300.475663@raynernix2.earthsci.unimelb.edu.au> <2014-03-06T14-11-29@devnull.Karl-Voit.at> <87zjl3za8h.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e015366b4567c9704f4003a26 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41932) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLqM1-00008I-KM for emacs-orgmode@gnu.org; Fri, 07 Mar 2014 03:42:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WLqM0-0005K0-Di for emacs-orgmode@gnu.org; Fri, 07 Mar 2014 03:42:05 -0500 Received: from mail-oa0-x22c.google.com ([2607:f8b0:4003:c02::22c]:46382) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLqM0-0005Jm-7P for emacs-orgmode@gnu.org; Fri, 07 Mar 2014 03:42:04 -0500 Received: by mail-oa0-f44.google.com with SMTP id n16so3850679oag.31 for ; Fri, 07 Mar 2014 00:42:03 -0800 (PST) In-Reply-To: <87zjl3za8h.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: Karl Voit , news1142@karl-voit.at, org mode , peter.julien.rayner@gmail.com --089e015366b4567c9704f4003a26 Content-Type: text/plain; charset=ISO-8859-1 Hi Peter and all Peter you wrote: I can flatten this list into a list of TODO and I can store it as a separate project that will be incorporated into the agenda view Do you mind giving a short example on how thats done? id be very interested in using this myself best Z On Thu, Mar 6, 2014 at 4:13 PM, Matt Lundin wrote: > 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 > > --089e015366b4567c9704f4003a26 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Peter and all
Peter you wrote:<= /span>
I can flatten this list into a list of TODO and I can store it as a=
<= span style=3D"font-family:arial,sans-serif;font-size:11.333333015441895px">= separate project that will be incorporated into the agenda view

Do you mind giving a short example on how = thats done? id be very=A0interested=A0in using this myself

best

Z


On Thu, Mar 6, 2014 at 4:13 PM,= Matt Lundin <mdl@imapmail.org> wrote:
Karl Voit <devnull@Karl-V= oit.at> writes:

> * Peter Rayner <pe= ter.julien.rayner@gmail.com> 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 headin= gs 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, whic= h 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 u= se
:TRIGGER: chain-siblings-scheduled(NEXT).

Best,
Matt


--089e015366b4567c9704f4003a26--