From: SabreWolfy <sabrewolfy@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Best practice for canceled/moved recurring events
Date: Fri, 22 Jul 2016 13:29:25 +0000 (UTC) [thread overview]
Message-ID: <loom.20160722T152140-164@post.gmane.org> (raw)
I have a meeting at 09:00 every Monday:
--8<---------------cut here---------------start------------->8---
* Diary
** TODO Weekly Meeting
DEADLINE: <2016-07-18 Mon 09:00 +1w>
--8<---------------cut here---------------end--------------->8---
What is the best way of dealing with scenarios where (1) the meeting "next
week" is on the Wednesday and (2) the meeting "two weeks" after that (or
whatever) is canceled?
Should I create a large set of time-shift entries for each week individually
and edit accordingly?
next reply other threads:[~2016-07-22 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 13:29 SabreWolfy [this message]
2016-07-24 15:27 ` Best practice for canceled/moved recurring events Jason Riedy
2016-08-02 19:10 ` Christoph LANGE
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=loom.20160722T152140-164@post.gmane.org \
--to=sabrewolfy@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).