From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Engster <deng@randomsample.de>
Subject: Re: org-caldav feedback
Date: Wed, 23 Jan 2013 21:16:07 +0100
Message-ID: <87a9rzy7so.fsf@engster.org>
References: <CAPaq-gM97iOO8siF0RijHxe6Q7+Q3kO+syGzQHugmjCVEtSh4g@mail.gmail.com>
	<87wqvb1vh4.fsf@engster.org>
	<CAPaq-gPwJvpxQMcfGPKH_fpwSq+hZ58O1eWwk5fN3CgL=5baHw@mail.gmail.com>
	<87obgi2v9t.fsf@engster.org>
	<CAPaq-gOW8d8nDqvyNGwtSmd7=rM2ZKD_dG-eHdzwt-F-SR1GUA@mail.gmail.com>
	<87fw1u2pdp.fsf@engster.org>
	<CAPaq-gP65LR0NcHsiy4ChYsNwjEnOUBWZ65BNZ6B6Eo_Q0TCng@mail.gmail.com>
	<87boch2dik.fsf@engster.org>
	<CAPaq-gMv=HkWjE==3=HhOiYPOiLuKOYaZkpzjuJ9JPU2q76i_w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:45480)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <deng@randomsample.de>) id 1Ty6k4-0007BS-QL
	for emacs-orgmode@gnu.org; Wed, 23 Jan 2013 15:16:18 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <deng@randomsample.de>) id 1Ty6k3-0004ns-I5
	for emacs-orgmode@gnu.org; Wed, 23 Jan 2013 15:16:16 -0500
Received: from randomsample.de ([83.169.19.17]:36112)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <deng@randomsample.de>) id 1Ty6k3-0004nc-94
	for emacs-orgmode@gnu.org; Wed, 23 Jan 2013 15:16:15 -0500
In-Reply-To: <CAPaq-gMv=HkWjE==3=HhOiYPOiLuKOYaZkpzjuJ9JPU2q76i_w@mail.gmail.com>
	(Torsten Wagner's message of "Wed, 23 Jan 2013 15:38:10 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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 <torsten.wagner@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>

Torsten Wagner writes:
> 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
> =A0timestamp within the context of the new text?!) but for now, I would s=
uggest
> 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 ;) ).

Yes, something like this needs to be done. As I've written in my last
mail, I'm hoping for a more general solution. I'm guessing that
org-elements can help me with this, but I haven't yet looked at it in
detail.

> In=A0addition a new=A0variable
>
> org-caldav-timestamp-pos which can be either "header" or "body"
>
> could indicate where to place the timestamp for a new entry coming from c=
aldav.

Hmm. What are the advantages of putting it in the header?

-David