org-trigger-hook vs. org-after-todo-state-change-hook

org-trigger-hook vs. org-after-todo-state-change-hook

[Marcin Borkowski]

Hi all,

org-trigger-hook vs. org-after-todo-state-change-hook:

which one to choose?  (I want to execute some code when an item is
marked as done.)  Why do both of them exist?

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: org-trigger-hook vs. org-after-todo-state-change-hook

[Nick Dokos]

Marcin Borkowski <mbork@mbork.pl> writes:

> org-trigger-hook vs. org-after-todo-state-change-hook:
>
> which one to choose?  (I want to execute some code when an item is
> marked as done.)  Why do both of them exist?
>

The trigger hook functions take a proplist argument which provides a lot
more information to the function than what is available to the
after-todo-state-change functions (which take no argument): the latter
can only know what the new state is going to be (through a global
variable); as a result, they can be much simpler than the trigger
functions, so if you don't need the extra info, after-todo is probably
the way to go.

-- 
Nick