George Pearson <[email protected]> writes: > On further thought, live archiving of repeater done-timestamps could > happen automatically if the org code was changed to allow a destination > for the done-timestamps. > > In that case, IF the item has a level 2 repeater and IF it has an > archive property, then set the destination to the archive property > location (which would be the archive file and duplicate headline there.) > > At least without hints, this seems beyond my ability, due to my elisp & > org coding inexperience, which is not helped by the limited or no > comments in some of the related code.
Maybe you can use `org-after-todo-state-change-hook'. Or, alternatively, `org-add-log-setup' - if you look inside, it is exactly where the target is set (`org-log-note-marker'). > Btw, I've been using org mode since 2008, so you can imagine how many > excess repeater done-timestamps are in my org file, and I have lots of > repeaters too! I least I now have some time to fool around with this ... > > Of course, I could probably just delete a lot of the older history, but > that seems more trouble than just archiving the whole thing - disk space > is cheap! I personally just let the notes accumulate, duplicate the task manually, rename it, and shove the whole old renamed version into archive files. -- 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>
