emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: access to specific instance(s) of past recurring event(s)
Date: Mon, 26 Sep 2022 06:54:20 +1000	[thread overview]
Message-ID: <86fsgfrx3h.fsf@gmail.com> (raw)
In-Reply-To: <0D6C3CE3-D839-454A-B48E-E43B83C99C1F@gmail.com>


Mark Barton <mbarton98@gmail.com> writes:

> 
>
>> On Sep 25, 2022, at 5:44 AM, Saša Janiška <sjaniska@atmarama.net> wrote:
>> 
>> When looking for some solution I've stumbled upon this (old) post
>> https://karl-voit.at/2017/01/15/org-clone-subtree-with-time-shift/ which utilizes
>> *org-clone-subtree-with-time-shift*.
>
> I also use this method for some of my reoccurring events. I usually create a year's worth
> of clones and then a task to clone more for next year. It is nice to be able to
> remove/adjust some of the subtree entries to accommodate holidays.
>
> When I don't use this method for a reoccurring event then I usually just schedule a
> repeating task and then have my notes in that task to record what happened each time.
>
> Mark

That is pretty much my work flow as well. Sometimes cloning is useful
because you actually want separate 'entries' and want to retain
them. Other times, you actually want all the notes associated with some
repeating 'thing' to be kept together. Having this flexibility is very
useful.


  parent reply	other threads:[~2022-09-25 20:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 14:25 access to specific instance(s) of past recurring event(s) Mark Barton
2022-09-25 14:38 ` Saša Janiška
2022-09-25 20:54 ` Tim Cross [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-25 12:16 Saša Janiška
2022-09-25 13:46 ` Fraga, Eric
2022-09-25 14:35   ` Saša Janiška
2022-09-25 18:10 ` Bob Newell

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=86fsgfrx3h.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).