Michael Heerdegen writes:
> Do you think others may want the same and it could be worth to implement
> this feature?
It should be not too hard to implement. For example, one can add another
possible value of org-log-repeat. Patches welcome ;)
Best,
Ihor
Ihor Radchenko writes:
> You are right. Since this is hard-coded, you may have to use :around
> advice to disable org-log-setup: [...]
Do you think others may want the same and it could be worth to implement
this feature?
Michael.
Michael Heerdegen writes:
> As far as I understand, the logging is implemented in
> `org-auto-repeat-maybe', and the thing I do not want is caused by the
> `org-add-log-setup' call, and that is done unconditionally unless
> `org-log-repeat's value is nil. Which I don't want because this would
>
Ihor Radchenko writes:
> > Is there a way to get only the :LAST_REPEAT: prop logged, without the
> > ever-growing list?
>
> I guess you can try to play with org-log-done and org-log-repeat
> variables.
Thanks. But as far as I recall, that's what I already tried and it
didn't help.
As far as I
Michael Heerdegen writes:
> Is there a way to get only the :LAST_REPEAT: prop logged, without the
> ever-growing list?
I guess you can try to play with org-log-done and org-log-repeat variables.
Best,
Ihor
Hello,
for some entries I use the logrepeat feature (enabled by setting the
LOGGING property of the entry).
I get a :LAST_REPEAT: property that I (always) want, and also a complete
log I do not (always) want, in the form of a growing list of
- State "DONE" from "XYZ" [2021-01-19 Di 12:01]
style
