emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Matt Lundin <mdl@imapmail.org>
To: Karl Voit <devnull@Karl-Voit.at>
Cc: news1142@Karl-Voit.at, emacs-orgmode@gnu.org
Subject: Re: automatic scheduling of next task in project
Date: Thu, 06 Mar 2014 08:13:02 -0600	[thread overview]
Message-ID: <87zjl3za8h.fsf@fastmail.fm> (raw)
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")

Karl Voit <devnull@Karl-Voit.at> writes:

> * Peter Rayner <peter.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 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

next prev parent reply	other threads:[~2014-03-06 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 11:04 automatic scheduling of next task in project Peter Rayner
2014-03-06 13:15 ` Karl Voit
2014-03-06 14:13   ` Matt Lundin [this message]
2014-03-07  8:42     ` Xebar Saram

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zjl3za8h.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=devnull@Karl-Voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).