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 > 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 ;) ).
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 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. Hmm. What are the advantages of putting it in the header? -David
