[Orgmode] Re: ics file not understood by google calendar

[Vagn Johansen]

Carsten Dominik <address@hidden> writes:

> On Feb 2, 2010, at 9:18 PM, Vagn Johansen wrote:

>> I tried git bisect with "grep -R VTODO .". It seems that org-mode has
>> always used VTODO so it is not a regression in org-mode.  I think the
>> problem is caused by a change in google calendar. They no longer
>> support VTODO.
>
> In this case, you just need to export to ical files without TODO
> stuff, i.e.
>
> (setq org-icalendar-include-todo nil)   ; this is already the default,
> actually

This just gives me an empty ics file!

For example

    #+STARTUP: content hidestars

    * TODO feb7-todo
      SCHEDULED: <2010-02-07 Sun>
    * TODO feb8-todo
      SCHEDULED: <2010-02-08 Mon>
    * feb9-event
      SCHEDULED: <2010-02-09 Tue>
    * feb10-event
      SCHEDULED: <2010-02-10 Wed>
    * EOF

(http://ozymandias.dk/test/test6275.org)

With my custom setting 

  '(org-icalendar-include-todo (quote all))

I have feb7-todo and feb8-todo in my ics file after a C-C C-e i
export. The other two are nowhere to be seen.
(http://ozymandias.dk/test/test6275.ics)

Your suggestion

  '(org-icalendar-include-todo nil)

gives me an ics-file with no entries.

Are you saying there is a way to get non-TODO entries into the ics
file?

By the way, org-print-icalendar-entries is really difficult to
understand. Maybe you could split it up. The function appears to
generate VTODOs when org-icalendar-include-todo is non-nil and VEVENTs
when the timestamp begins with <%%. Is the latter related to the diary
time-format?

>
> So I guess this case is closed?

Maybe. If org-mode works as documented then perhaps all is good.

I can work around my problem by changing org-icalendar.el to use
VEVENT where it now uses VTODO and only use TODOs in org-files. This
will generate an ics-file with the TODO entries when
org-icalendar-include-todo is non-nil.

I do not know much about the ics format so I cannot tell you what is
the correct thing to do here. It would be useful if other people could
tell about their experience in importing ics-files into various tools
to gauge the VTODO support. Maybe only VEVENT should be used.

-- 
Vagn Johansen