Hello,
Allen Li writes:
> * lisp/org-agenda.el (org-agenda-list-stuck-projects): Store the redo
> command in a text property so it is found correctly.
>
> `org-agenda-redo' checks the `org-redo-cmd' text property, not
> `org-agenda-redo-command'.
>
> TINYCHANGE
Applied. Thank you.
Regards,
--
maybe i got that backward.
my note is: "fixme bug in org: either if you do g, it will ignore restriction
lock or you have to manually remove restriction lock. the best
would be for g to preserve the restriction lock even though it
has been removed."
On 4/20/17, Samuel Wales wrote:
> in case it
in case it isn't already considered, i think storing the conditions of
the original call applies to many agenda calls. i run into this issue
with the following old code. i set a restriction lock, and run
agenda, but g runs agenda without the restriction lock.
(defun alpha-org-agenda-subtree (&op
* lisp/org-agenda.el (org-agenda-list-stuck-projects): Store the redo
command in a text property so it is found correctly.
`org-agenda-redo' checks the `org-redo-cmd' text property, not
`org-agenda-redo-command'.
TINYCHANGE
---
lisp/org-agenda.el | 6 +-
1 file changed, 5 insertions(+), 1 d
