Add clarification

This commit is contained in:
Bram Schoenmakers 2022-11-26 15:00:40 +01:00
parent 22bdd3d76d
commit df72a38bdb
2 changed files with 2 additions and 2 deletions

View file

@ -129,7 +129,7 @@ My vertico-repeat setup.
#+begin_src org :tangle gists/execute-code-on-task-state-change.org
The function below executes Lisp forms stored in properties of a TODO item, when it reaches a certain state. The function is supposed to be added to the =org-after-todo-state-change-hook=.
The property should be named =ON_<STATE>= where =STATE= is a state defined in =org-todo-keywords=. See also the example task below.
The property should be named =ON_<STATE>= where =STATE= is a state defined in =org-todo-keywords=. See also the example task below (open this file in [[https://apps.bram85.nl/gitea/bram/gists/raw/branch/main/gists/execute-code-on-task-state-change.org][raw mode]] to see the properties).
,#+begin_src elisp
(defun my/task-state-event-handler ()

View file

@ -1,6 +1,6 @@
The function below executes Lisp forms stored in properties of a TODO item, when it reaches a certain state. The function is supposed to be added to the =org-after-todo-state-change-hook=.
The property should be named =ON_<STATE>= where =STATE= is a state defined in =org-todo-keywords=. See also the example task below.
The property should be named =ON_<STATE>= where =STATE= is a state defined in =org-todo-keywords=. See also the example task below (open this file in [[https://apps.bram85.nl/gitea/bram/gists/raw/branch/main/gists/execute-code-on-task-state-change.org][raw mode]] to see the properties).
#+begin_src elisp
(defun my/task-state-event-handler ()