emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Carsten Dominik
Subject: Re: [Orgmode] Re: ics file not understood by google calendar
Date: Thu, 4 Feb 2010 07:30:39 +0100


On Feb 3, 2010, at 10:33 PM, Vagn Johansen wrote:

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?

Yes.

Any entries that have a plain time stamp like

* meeting with Peter
  <2010-02-07 Sun>

will create a VEVENT

Also, you can configure the variables org-icalendar-use-deadlines
and org-icalendar-use-scheduled to make these timestamps become
VEVENT as well.  By default they are set up to use these special
time stamps as start date and due date in TODO entries, but you
can use them for more.  Take a look at the entire customization group
org-export-icalendar, there might be more stuff you'd find useful.


By the way, org-print-icalendar-entries is really difficult to
understand.

Yes. This function was grown, in the absence of predators.  No
intelligent design here... :-)

Maybe you could split it up.

It works, and I do not want to break it. Feel free to break it up, test it extensively (!) and send me a patch.

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?

Yes, you can use diary-like sexp functions to create complicated dates.

Hope this helps

- Carsten




reply via email to

[Prev in Thread] Current Thread [Next in Thread]