emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: depending TODOs, scheduling following TODOs automatically
Date: Thu, 11 Oct 2007 17:53:37 +0100	[thread overview]
Message-ID: <87641d1tke.fsf@bzg.ath.cx> (raw)
In-Reply-To: <8a4d082edbc607440d4f12604b2f6332@science.uva.nl> (Carsten Dominik's message of "Thu, 11 Oct 2007 16:46:33 +0200")

Carsten Dominik <dominik@science.uva.nl> writes:

> I have read this discussion with great interest, and I would like to
> add a few thoughts.

I guess some of us were waiting for that -- thanks for sorting this
out :)

> First, let me say that I was surprised that quite a few people are so
> keen to see this kind of features.

Well, maybe there are too few tutorials out there demonstrating how
people actually use Org, but everytime someone sends an example I'm
amazed how this example looks so "personal" and add something new to
what I could imagine. 

Given the number of different persons using Org (at least the number of
emacs-orgmode@gnu.org subscribers?) I wouldn't be surprised that people
come up with clever use of TRIGGERS in their own planning habits.  Even
better if they share it through tutorials...

> - first of all, I believe we can keep the question of adressing an
> item (using GUIDs or relations like "next TODO item in the subtree")
> completely separate from the mechanism by which Org-mode triggers an
> action.

100% agreed (see my previous post.)

>   So we would have a property that contains a Lisp form, and that lisp
> form would be evaluated at that moment.
>   TRIGGER would then mean to perform actions in other entries.

Just to make things perfectly clear - here is the process (as I
understand it) :

1. describe the last change performed on a headline in a Lisp form
2. feed any TRIGGER with the Lisp form from 1. and perform actions

Is that right?  

>   The detailed implementation would then be a number of Lisp functions
> that take as arguments a *single* structure that contains all the info
> of the change, for example a property list like
>
>       (list :type 'TODOSTATE :from nil %to "INPROGRESS" ....)

The uncertainty of my understanding relies on the fact that I'm not sure
whether this implementation is supposed to describe the TRIGGER function
or the Lisp form from the first step of the process, as described above.

Thanks for any further clarification!

-- 
Bastien

  parent reply	other threads:[~2007-10-11 15:53 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08  6:56 depending TODOs, scheduling following TODOs automatically Rainer Stengele
2007-10-08 13:26 ` Denis Bueno
2007-10-08 13:43   ` Russell Adams
2007-10-08 13:52     ` Russell Adams
2007-10-08 19:48       ` Carsten Dominik
2007-10-08 20:12         ` Russell Adams
2007-10-09 10:13           ` Carsten Dominik
2007-10-08 14:49     ` Eddward DeVilla
2007-10-08 20:55       ` Bastien
2007-10-08 20:26         ` Adam Spiers
2007-10-09  2:15           ` Bastien
2007-10-09  3:03             ` John Wiegley
2007-10-09  3:47               ` Eddward DeVilla
2007-10-09  9:27                 ` Richard G Riley
2007-10-09 14:39                   ` Eddward DeVilla
2007-10-10 17:20                     ` Bastien
2007-10-09 10:35                 ` Bastien
2007-10-09 10:32               ` Bastien
2007-10-11 14:46             ` Carsten Dominik
2007-10-11 15:53               ` pete phillips
2007-10-11 16:22                 ` Sebastjan Trepca
2007-10-11 16:37                 ` Russell Adams
2007-10-11 17:10                   ` pete phillips
2007-10-11 17:55                     ` Russell Adams
2007-10-11 18:45                       ` pete phillips
2007-10-14  1:01                         ` Charles Cave
2007-10-14  2:42                           ` Bastien
2007-10-11 19:46                       ` Bastien
2007-10-11 21:12                       ` Rainer Stengele
2007-10-11 21:19                         ` Leo
2007-10-11 23:54                           ` Piotr Zielinski
2007-10-12  3:14                             ` Eddward DeVilla
2007-10-12 13:50                               ` Bastien
2007-10-12 17:09                         ` Jason F. McBrayer
2007-10-12 17:03                 ` Jason F. McBrayer
2007-10-11 16:53               ` Bastien [this message]
2007-10-12  9:21               ` John Wiegley
2007-10-08 20:35         ` Eddward DeVilla
2007-10-09  2:42           ` Bastien
2007-10-09  2:01             ` Russell Adams
2007-10-09  3:35               ` Eddward DeVilla
2007-10-09  3:59                 ` Russell Adams
2007-10-09  4:55                   ` Eddward DeVilla
2007-10-09 10:42                   ` Bastien
2007-10-09  3:37               ` Bastien
2007-10-09  2:58             ` Eddward DeVilla
2007-10-09 10:41               ` Bastien
2007-10-09 14:53                 ` Eddward DeVilla
2007-10-11 12:44                   ` Bastien
2007-10-11 12:22                     ` Russell Adams
2007-10-11 14:03                       ` Bastien
2007-10-11 13:21                         ` Russell Adams
2007-10-11 13:31                         ` Eddward DeVilla
2007-10-12  9:13                         ` John Wiegley
2007-10-09  9:44       ` Christian Egli
2007-10-09 10:53         ` Bastien
2007-10-09 15:21         ` Eddward DeVilla
2007-10-11 12:44           ` Bastien

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=87641d1tke.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).