exec code on task state progression

exec code on task state progression

[Richard Riley]

What would be the best approach, if at all possible, to having org
manage tasks which allow me set dates for a task to be scheduled and
then let me manually progress/cycle that task and have it then invoke
code/scripts?

e.g I might have a task which is "Update Org" which is scheduled as a
repeat task once a week, When marking it done for that week (to drop it
from my agenda) it also runs a shell script which goes ahead and
executes a small bash script which does a git pull etc. I might also use
it for, say, reminding me to send an email to certain customers every
month and actually invoke the necessary gnus functions via elisp when I
set it to "done".

I realise I can use babel to manually exec code blocks and that org can
also follow shell and elisp links, but how to easily tie that in with
task flow?

Re: exec code on task state progression

[David Maus]

[-- Attachment #1.1: Type: text/plain, Size: 1608 bytes --]

Richard Riley wrote:

>What would be the best approach, if at all possible, to having org
>manage tasks which allow me set dates for a task to be scheduled and
>then let me manually progress/cycle that task and have it then invoke
>code/scripts?

Maybe something like this: Store the name of the function to be
executed in a property and define a function which is run in
`org-after-todo-state-change-hook' that reads this property and
executes the function if, say, the state was changed to "DONE".

(defun dmj:execute-func-after-todo-change ()
  "Execute function in exec_func property if entry changes to DONE."
  (when (string= state "DONE")
    (let ((func (intern (org-entry-get nil "exec_func"))))
      (if (fboundp func) (funcall func)))))

(add-hook 'org-after-todo-state-change-hook 'dmj:execute-func-after-todo-change)

For the update part you might want to look at el-get.el[1]:

,----
| Short Story: el-get allows you to install and manage elisp code for
| Emacs. It supports lots of differents types of sources and is able to
| install them, update them and remove them, but more importantly it
| will init them for you.
|
| That means it will care about require ing the features you need, load
| ing the files, setting the Info paths so that C-h i shows the new
| documentation you now depend on, and finally call your own :after
| function for you to setup the extension. Or call it a package.
`----

I did not try it (yet), but this looks sweet.

HTH,
  -- David

[1] http://github.com/dimitri/el-get
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode