From: Michael Brand <michael.ch.brand@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Org Mode" <emacs-orgmode@gnu.org>
Subject: Re: Adding support for limits and exclusions to iCal recurring events
Date: Wed, 24 Jul 2013 18:01:43 +0200 [thread overview]
Message-ID: <CALn3zoh9Y9QU3=o40Y-StN3W1SHB9dmDfXKM+wkf3ahHAHRRdA@mail.gmail.com> (raw)
In-Reply-To: <87ip005p5b.fsf@gmail.com>
Hi Nicolas
On Wed, Jul 24, 2013 at 10:38 AM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> I'm clearly no Agenda specialist. I thought a DEADLINE would end
> a repeated event already.
No, DONE shifts it to the repeat date and like this it will never end.
> If it's not the case, does it make sense to implement it too?
In this case I would vote for to use a new property.
An example like
* TODO send weekly report
DEADLINE: <2013-07-27 Sat 18:00 ++1w -1d>
could then be terminated with
* TODO send weekly report until end of terminated contract
DEADLINE: <2013-07-27 Sat 18:00 ++1w -1d>
END_DATE: <2013-12-31 Tue>
When implementing this, consider also whether the END_DATE should be an
agenda entry on its own and of which kind, warning period etc. I tried
to make an example that shows this issue.
Michael
next prev parent reply other threads:[~2013-07-24 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 15:55 Adding support for limits and exclusions to iCal recurring events Toke Høiland-Jørgensen
2013-07-22 11:45 ` Nicolas Goaziou
2013-07-22 14:56 ` Toke Høiland-Jørgensen
2013-07-24 8:38 ` Nicolas Goaziou
2013-07-24 16:01 ` Michael Brand [this message]
2013-07-24 17:25 ` Toke Høiland-Jørgensen
2013-07-27 21:11 ` Nicolas Goaziou
2013-07-27 22:16 ` Toke Høiland-Jørgensen
2013-07-24 18:23 ` David Rogers
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='CALn3zoh9Y9QU3=o40Y-StN3W1SHB9dmDfXKM+wkf3ahHAHRRdA@mail.gmail.com' \
--to=michael.ch.brand@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=toke@toke.dk \
/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).