emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: eckl.r@gmx.de
Cc: emacs-orgmode@gnu.org
Subject: Re: org-caldav: Sync Org with external calendars through CalDAV (Owncloud, Google, ...)
Date: Thu, 26 Jul 2012 21:03:43 +0200	[thread overview]
Message-ID: <87629any40.fsf@engster.org> (raw)
In-Reply-To: <00d901cd6b4d$c37f0df0$4a7d29d0$@gmx.de> (Robert Eckl's message of "Thu, 26 Jul 2012 18:43:19 +0200")

Robert Eckl writes:
> Acutally, an appointment must not have any text outside the Properties

[...]

I think there's a bug in org-icalendar with regards to handling
tags. I'm getting an icalendar event like this:

BEGIN:VEVENT
UID:f90ec513423879f1e09c7c10fc0e15a9-orgmodecaldav
DTSTART:20120728T200000
DTEND:20120728T210000
SUMMARY:TerminTest                                                      :Tag:
DESCRIPTION: <2012-07-28 Sat 20:00-21:00>\n\nSomewhat
LOCATION: Büro
CATEGORIES:Tag,Termine
END:VEVENT

Putting this event generates an error from Google, but I think it's due
to the :Tag: in the SUMMARY line; the DESCRIPTION looks OK to me.

> Combined with MobileOrg this behavior is bothering.
>
> If an appointment is scheduled, it will not be synced if there is no active
> timestamp without the keyword SCHEDULED:

Again, this looks like a problem with org-icalendar. I'm not very
familiar with that code, but I'll look into it.

Thanks for testing,
David

  reply	other threads:[~2012-07-26 19:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 16:43 org-caldav: Sync Org with external calendars through CalDAV (Owncloud, Google, ...) Robert Eckl
2012-07-26 19:03 ` David Engster [this message]
2012-07-26 20:55   ` David Engster
2012-07-30  2:01   ` Luis Anaya
  -- strict thread matches above, loose matches on Subject: below --
2012-07-14 19:12 David Engster
2012-07-20 16:36 ` David Engster
2012-07-20 16:55   ` Mehul Sanghvi
2012-07-20 18:00   ` Jason F. McBrayer
     [not found]   ` <deng@randomsample.de>
2012-07-20 18:29     ` Nick Dokos
2012-07-23 19:25   ` Suvayu Ali
2012-07-26 17:10   ` Aurélien Aptel
2012-07-25  8:18 ` Torsten Wagner
2012-07-25 19:02   ` David Engster
2012-07-27 14:49 ` Torsten Wagner
2012-07-28 12:05   ` David Engster
2012-08-03  7:46 ` Bastien
2012-08-03 12:48   ` David Engster
2012-08-04  8:27     ` Bastien
2012-08-05 18:41       ` David Engster
2012-12-03 12:35         ` Stephen Eglen
2012-12-03 19:50           ` David Engster
2012-12-04 10:29             ` Suvayu Ali
2012-12-04 10:45               ` Stephen Eglen
2012-12-04 11:19                 ` Stephen Eglen
2012-12-04 19:19                   ` David Engster
2012-12-05 11:40                     ` Stephen Eglen
2012-12-05 12:15                       ` Stephen Eglen
2012-12-04 19:27               ` David Engster
2012-09-11 14:17 ` Philipp Haselwarter

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=87629any40.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=eckl.r@gmx.de \
    --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).