Aaron Zeng <z...@bcc32.com> writes:
> org-log-reschedule's docstring says that the org-schedule and
> org-agenda-schedule commands respect the LOGGING property for a
> subtree, but the behavior I observe seems to indicate the LOGGING
> property has in fact no effect.
>
> ## Reproduction steps
> ...
Confirmed.
Not urgent.
Same for org-log-redeadline.
The attached diff is showing what should potentially be done, except
that `org-local-logging' is not called from org-schedule/deadline, and
does not work unless the user changes a todo state in the buffer.
The general design of this feature is prone to bugs because it is
juggling dynamic state. I have a rewrite of this logic on refactor
branch. May better look after that one is finalized.
diff --git a/lisp/org.el b/lisp/org.el
index bc61a7c462..1ab86e961f 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -10057,12 +10057,13 @@ (defun org-local-logging (value)
;; Directly set the variables, they are already local.
(setq org-log-done nil
org-log-repeat nil
- org-todo-log-states nil)
+ org-todo-log-states nil
+ org-log-reschedule nil)
(dolist (w (split-string value))
(let (a)
(cond
((setq a (assoc w org-startup-options))
- (and (member (nth 1 a) '(org-log-done org-log-repeat))
+ (and (member (nth 1 a) '(org-log-done org-log-repeat org-log-reschedule))
(set (nth 1 a) (nth 2 a))))
((setq a (org-extract-log-state-settings w))
(and (member (car a) org-todo-keywords-1)
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
