From mboxrd@z Thu Jan 1 00:00:00 1970 From: Torsten Wagner Subject: Re: org-caldav feedback Date: Wed, 23 Jan 2013 15:38:10 +0100 Message-ID: References: <87wqvb1vh4.fsf@engster.org> <87obgi2v9t.fsf@engster.org> <87fw1u2pdp.fsf@engster.org> <87boch2dik.fsf@engster.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d042e0079b9d83104d3f5a444 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36103) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ty1Sx-000372-Qg for emacs-orgmode@gnu.org; Wed, 23 Jan 2013 09:38:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ty1Su-0000Qz-JM for emacs-orgmode@gnu.org; Wed, 23 Jan 2013 09:38:15 -0500 Received: from mail-pa0-f50.google.com ([209.85.220.50]:56663) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ty1Su-0000Qe-9p for emacs-orgmode@gnu.org; Wed, 23 Jan 2013 09:38:12 -0500 Received: by mail-pa0-f50.google.com with SMTP id hz10so4814674pad.9 for ; Wed, 23 Jan 2013 06:38:11 -0800 (PST) In-Reply-To: <87boch2dik.fsf@engster.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Torsten Wagner , Org Mode Mailing List --f46d042e0079b9d83104d3f5a444 Content-Type: text/plain; charset=ISO-8859-1 Hi David, time is correct now using "UTC" thanks a lot. My test suite runs fine with the SOGo server, so I'm guessing it has to > do with how you format your entries. Does this also happen when you put > the timestamp underneath the heading? > > Tested and you are right. Adding a timestamp in the body doesn't get lost during sync. Actually, I guess the problem is a combination of export and import to org-mode. During the export, the timestamp gets read in correctly, however, it get stripped from the Summary line (which is good). During the import, org-caldav does not find a timestamp in the body to update and does nothing (wild speculation). A possible solution would be to teach org-caldav to update the timestamp within the node header if available. I see the problem that you might changed the text in the summary field in the caldav calendar, which potentially mess up the header (where to place the old timestamp within the context of the new text?!) but for now, I would suggest to simply search for a timestamp within the node-header and update it by adding a new timestamp at the very end (but before tags ;) ). In addition a new variable org-caldav-timestamp-pos which can be either "header" or "body" could indicate where to place the timestamp for a new entry coming from caldav. Thanks again for this great work and I really appreciate your help and effort Torsten On a general note, I find manipulating Org entries rather delicate and > wonder why there are no helper functions to change things like headings, > timestamps, etc., which take care of the multitude of possibilities how > entries can be formatted. My guess is that org-elements might be the > solution for this, but I haven't looked at it yet... > > -David > --f46d042e0079b9d83104d3f5a444 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi David,

time is correct now using "UTC" than= ks a lot.


My test suite runs fine with the SOGo server, so I'm guessing it has to=
do with how you format your entries. Does this also happen when you put
the timestamp underneath the heading?

Tested and you are right. Adding a timestamp in the b= ody doesn't get lost during sync.
Actually, I guess the probl= em is a=A0combination=A0of export and import to org-mode.
During = the export, the timestamp gets read in correctly, however, it get stripped = from the Summary line (which is good).
During the import, org-caldav does not find a timestamp in the body to= update and does nothing (wild speculation).

A pos= sible solution would be to teach org-caldav to update the timestamp within = the node header if available.=A0
I see the problem that you might changed the text in the summary field= in the caldav calendar, which potentially mess up the header (where to pla= ce the old =A0timestamp within the context of the new text?!) but for now, = I would suggest to simply search for a timestamp within the node-header and= update it by adding a new timestamp at the very end (but before tags ;) ).= In=A0addition a new=A0variable

org-caldav-timestamp-pos which can be either "head= er" or "body"

could indicate where = to place the timestamp for a new entry coming from caldav.

Thanks again for this great work and I really appreciate your he= lp and effort

Torsten


=A0
=A0 =A0=A0

On a general note, I find manipulating Org entries rather delicate and
wonder why there are no helper functions to change things like headings, timestamps, etc., which take care of the multitude of possibilities how
entries can be formatted. My guess is that org-elements might be the
solution for this, but I haven't looked at it yet...

-David

--f46d042e0079b9d83104d3f5a444--