From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-orgmode@gnu.org
Subject: Re: N/A; icalendar export doesn't guarantee unique UIDs
Date: Thu, 10 May 2012 08:43:13 +0200 [thread overview]
Message-ID: <87havocz9a.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: 87pqadgqg7.fsf@thinkpad.tsdh.de
Tassilo Horn <thorn@fastmail.fm> writes:
> For example, I have entries like
>
> *** Meeting with Max
> :PROPERTIES:
> :ID: e1c32cb4-bd1f-4302-8067-1723d1958a88
> :END:
> <2012-03-13 Tue 12:00-13:00>
> <2012-03-21 Wed 15:00-16:00>
> <2012-03-29 Thu 10:00-11:00>
> <2012-04-10 Tue 12:00-13:00>
> <2012-04-18 Wed 11:00-11:30>
> <2012-04-25 Wed 10:00-11:00>
> <2012-05-10 Thu 12:00-13:00>
>
> They should show up at any date/time listed there. That's true for the
> org agenda with `org-agenda-skip-additional-timestamps-same-entry' set
> to nil. The icalendar export also creates multiple VEVENTS for the
> above org entry, *but they all have the same UID* (which is strictly
> VERBOTEN by the icalendar spec). The result is that the google calendar
> only shows one appointment, and that seems to be arbitrary. In the
> example above, it shows the meeting on 2012-04-18.
Another very related topic: Even when ignoring entries with multiple
timestamps, every icalendar item (VTODO, VEVENT, VJOURNAL) must have a
SEQUENCE number that has to be incremented when an entry changes
significantly (start, end, due, ..., see RFC 2445: 4.8.7.4).
I've read in the google calendar help group, that the google calendar
won't refresh items for which the UID is already known and the SEQUENCE
number didn't increase...
Bye,
Tassilo
prev parent reply other threads:[~2012-05-10 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 18:27 N/A; icalendar export doesn't guarantee unique UIDs Tassilo Horn
2012-05-10 6:43 ` Tassilo Horn [this message]
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=87havocz9a.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--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).