From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Michael Brand <michael.ch.brand@gmail.com>,
Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Adding support for limits and exclusions to iCal recurring events
Date: Sun, 28 Jul 2013 00:16:40 +0200 [thread overview]
Message-ID: <874nbfr6lz.fsf@toke.dk> (raw)
In-Reply-To: <87wqob1ze4.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 27 Jul 2013 23:11:47 +0200")
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> I think it would be less ambiguous to use ICALENDAR_UNTIL (or UNTIL),
> and apply RFC 5545:
Ah, that specifies it nicely, thanks (and that was what I was (trying
to) do with the patch). That would mean exporting the time as well as
the date for end times (and calling the property END_TIME, I suppose).
I would expect most people to just set and end date (i.e. a datestamp
without a time set); but that would also be supported by just going with
an end date.
I'll post an updated version of the patch for the iCal side of this
support once I get the time. Supporting it in the agenda will have to be
a separate patch since I'll probably need to do a bit more digging to
figure out how to do that properly; pointers? :)
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-07-27 22:17 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
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 [this message]
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=874nbfr6lz.fsf@toke.dk \
--to=toke@toke.dk \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@gmail.com \
--cc=n.goaziou@gmail.com \
/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).