emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vagn Johansen <gonz808@hotmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ics file not understood by google calendar
Date: Wed, 03 Feb 2010 22:33:41 +0100	[thread overview]
Message-ID: <m27hqu9f7u.fsf@hotmail.com> (raw)
In-Reply-To: 5314895F-526E-4641-8F41-D48456020DA5@gmail.com

Carsten Dominik <carsten.dominik@gmail.com> 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

  reply	other threads:[~2010-02-03 21:34 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
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 [this message]
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

  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=m27hqu9f7u.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 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).