At Fri, 17 Oct 2014 22:22:20 +0200, Nicolas Goaziou wrote: > This is because checkboxes (plain lists) are not related to TODO > keywords (headlines). There are TODO statistics cookies and checkbox > statistics cookies. Only the former run a hook once updated.
Thanks for clarifying. I hadn't understood that distinction. It occurred to me, after I sent my last e-mail, that someone might want one action after updating todo statistics and a different action after updating checkbox statistics. Using the same hook for both wouldn't be correct in that case. So let me update my issue report/feature request: -- If there is a hook to do something after updating todo statistics, then it would make sense to have a hook for updating checkbox statistics as well. That hook should be called with the same arguments (n-done n-not-done) so that the user could use one function for both, if desired. I can do this pretty easily and update the documentation. I don't have FSF papers signed, but I'm willing to get that ball rolling as well. But before spending any time on that, I want to ask if this is okay. I understand the objection against pressing org-after-todo-statistics-hook into service for checkboxes. If there's an objection against simply *having* a hook for checkboxes, I'm afraid I don't understand that. Thanks for your patience, hjh
