From: Vagn Johansen <gonz808@hotmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ics file not understood by google calendar
Date: Mon, 01 Feb 2010 20:47:11 +0100 [thread overview]
Message-ID: <m2k4uwagcg.fsf@hotmail.com> (raw)
In-Reply-To: BE5076E3-1615-4424-89BE-5A1B5BA51433@gmail.com
Carsten Dominik <carsten.dominik@gmail.com> writes:
> Hi Vagn,
>
> you are saying that this used to work out of the box and no longer does?
> Could you please git bisect to identify the offending commit?
Hi Carsten
Did you see my follow-up email? (reproduced below)
The problem appears to be caused by a change from VEVENT to VTODO in
org-icalendar.el. Of course, the change may be correct and google
calendar just does not support VTODO.
I just discovered some entries in google calendar which comes from an
org export to ics that was done half a year ago. They use VEVENT (as
opposed to VTODO).
This works
BEGIN:VEVENT
UID: TS-9164991C-7E1A-4D65-8A44-3674B236A836
DTSTART;VALUE=DATE:20090621
DTEND;VALUE=DATE:20090622
SUMMARY:leg press
DESCRIPTION: <2009-06-21 Sun>\nfik tips fra Martin om l...
CATEGORIES:privat
END:VEVENT
Does not work (test9365.ics)
BEGIN:VTODO
UID: TODO-34C3192F-21FE-48C1-BFD7-7934B51D03A3
DTSTART;VALUE=DATE:20100201
SUMMARY:feb1
CATEGORIES:test9365
SEQUENCE:1
PRIORITY:5
STATUS:NEEDS-ACTION
END:VTODO
If i change the first todo in test9365.ics to use VEVENT and save it
at http://ozymandias.dk/test/test9365c.ics then the event shows up in
google calendar.
--
Vagn Johansen
next prev parent reply other threads:[~2010-02-01 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 9:47 ics file not understood by google calendar Vagn Johansen
2010-01-31 10:09 ` Vagn Johansen
2010-02-01 6:43 ` Carsten Dominik
2010-02-01 19:47 ` Vagn Johansen [this message]
2010-02-02 6:14 ` Carsten Dominik
2010-02-02 20:18 ` Vagn Johansen
2010-02-03 10:37 ` Carsten Dominik
2010-02-03 21:33 ` Vagn Johansen
2010-02-04 6:30 ` Carsten Dominik
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=m2k4uwagcg.fsf@hotmail.com \
--to=gonz808@hotmail.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.