From: Mark Barton <mbarton98@gmail.com>
To: "Renaud Bussières" <contact@renaudbussieres.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: What's the proper way to define a recurring event
Date: Sat, 14 Dec 2024 10:15:41 -0800 [thread overview]
Message-ID: <90071988-6DEE-4075-8EEB-8B3DDF960AAA@gmail.com> (raw)
In-Reply-To: <87bjxe2lwa.fsf@renaudbussieres.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
> On Dec 14, 2024, at 9:51 AM, Renaud Bussières via General discussions about Org-mode. <emacs-orgmode@gnu.org> wrote:
>
> Let's say I want to insert my yoga class in my Agenda. This class starts on date X, it is planned to repeat every week, for 8 weeks. In my "agenda.org <http://agenda.org/>" file I would write:
Another option I have used is to create the header like below for Yoga Class followed by an org-timestamp.
* Events
** Yoga Class <2024-12-16 Mon>
*** Notes
Now while on the Yoga Class header, invoke M-x org-clone-subtree-with-time-shift.
It will prompt for how many clones, 7 in this case, and then the time-shift, +1w
** Yoga Class <2024-12-23 Mon>
*** Notes
** Yoga Class <2024-12-30 Mon>
*** Notes
** Yoga Class <2025-01-06 Mon>
*** Notes
** Yoga Class <2025-01-13 Mon>
*** Notes
** Yoga Class <2025-01-20 Mon>
*** Notes
** Yoga Class <2025-01-27 Mon>
*** Notes
** Yoga Class <2025-02-03 Mon>
*** Notes
What I like about this approach is that I can store unique notes for each one and archive really old entries. For unknown length of time cases, I will usually clone a year's worth at a time and put a reminder to clone more.
Mark
[-- Attachment #2: Type: text/html, Size: 3269 bytes --]
next prev parent reply other threads:[~2024-12-14 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 17:51 What's the proper way to define a recurring event Renaud Bussières via General discussions about Org-mode.
2024-12-14 18:15 ` Mark Barton [this message]
2024-12-17 17:21 ` Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90071988-6DEE-4075-8EEB-8B3DDF960AAA@gmail.com \
--to=mbarton98@gmail.com \
--cc=contact@renaudbussieres.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.