From: Ihor Radchenko <firstname.lastname@example.org> To: Gerardo Moro <email@example.com> Cc: emacs-orgmode <firstname.lastname@example.org> Subject: Re: Archiving repeated tasks under corresponding date tree for each repeated item Date: Tue, 17 Nov 2020 17:31:23 +0800 [thread overview] Message-ID: <87ft58nxck.fsf@localhost> (raw) In-Reply-To: <CAF4Fj9hFkJLPdfyEKketPQd2vjc3jNS=E9TcRoiW4kGn+be1iQ@mail.gmail.com> > I actually now realized that your function will not unfortunately archive > each logged item (those located in the logbook) in its corresponding date > (!). > What it will do is to archive the whole tree under today's date without > deleting it from the original org file. You are right. It is expected behaviour. That's why I suggested to run it in org-trigger-hook, which will trigger at the day and time when you mark the task DONE. Best, Ihor Gerardo Moro <email@example.com> writes: > Hi again, > > I actually now realized that your function will not unfortunately archive > each logged item (those located in the logbook) in its corresponding date > (!). > What it will do is to archive the whole tree under today's date without > deleting it from the original org file. > > For instance, > > * TODO REPEATED TASK SAMPLE > SCHEDULED: <2020-11-30 Mon +20d> > :PROPERTIES: > :STYLE: habit > :LAST_REPEAT: [2020-11-09 Mon 22:28] > :END: > :LOGBOOK: > - State "DONE" from "TODO" [2020-11-15 Sun 22:28] > - State "DONE" from "STARTED" [2020-11-14 Sat 22:17] > - State "DONE" from "STARTED" [2020-11-13 Fri 22:17] > - State "DONE" from "STARTED" [2020-11-11 Wed 22:17] > > If I position myself in any point in this entry, when I execute the > function it will archive the whole tree+subtree under today's date (the > date when it was archived). > The behaviour I was expecting is to archive each of the logged tasks under > their corresponding date (on the 11th, 13th, 14th and 15th of November). > Just to be clear :) > G > > El lun., 16 nov. 2020 a las 17:21, Gerardo Moro (<firstname.lastname@example.org>) > escribió: >
next prev parent reply other threads:[~2020-11-17 9:34 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CAF4Fj9hjjQ98gGe7hRp0tU4qPtZ-ekUUpO9niNpJ+s31g2buOA@mail.gmail.com> 2020-10-24 4:06 ` Gerardo Moro 2020-10-29 7:01 ` Gerardo Moro 2020-11-02 14:18 ` Julius Dittmar 2020-11-03 5:52 ` Ihor Radchenko 2020-11-12 7:59 ` Gerardo Moro 2020-11-12 10:27 ` Ihor Radchenko 2020-11-16 15:21 ` Gerardo Moro 2020-11-17 8:58 ` Gerardo Moro 2020-11-17 9:31 ` Ihor Radchenko [this message] 2020-11-17 12:00 ` Gerardo Moro 2020-11-17 12:31 ` Ihor Radchenko 2020-11-17 12:57 ` Gerardo Moro 2020-11-17 13:12 ` Ihor Radchenko 2020-11-17 15:35 ` Gerardo Moro 2020-11-17 15:59 ` Ihor Radchenko 2020-11-17 16:15 ` Gerardo Moro 2020-11-18 5:36 ` Ihor Radchenko 2020-11-18 8:35 ` Gerardo Moro
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=87ft58nxck.fsf@localhost \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Archiving repeated tasks under corresponding date tree for each repeated item' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).