[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] org-caldav feedback
From: |
David Engster |
Subject: |
Re: [O] org-caldav feedback |
Date: |
Wed, 23 Jan 2013 21:16:07 +0100 |
User-agent: |
Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2.50 (gnu/linux) |
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
- Re: [O] org-caldav feedback, (continued)
- Re: [O] org-caldav feedback, David Engster, 2013/01/21
- Re: [O] org-caldav feedback, Torsten Wagner, 2013/01/22
- Re: [O] org-caldav feedback, David Engster, 2013/01/22
- Re: [O] org-caldav feedback, Eric S Fraga, 2013/01/23
- Re: [O] org-caldav feedback, Torsten Wagner, 2013/01/23
- Re: [O] org-caldav feedback, David Engster, 2013/01/23
- Re: [O] org-caldav feedback, Eric S Fraga, 2013/01/23
- Re: [O] org-caldav feedback, David Engster, 2013/01/23
- Re: [O] org-caldav feedback, Eric S Fraga, 2013/01/23
- Re: [O] org-caldav feedback, Torsten Wagner, 2013/01/23
- Re: [O] org-caldav feedback,
David Engster <=
Re: [O] org-caldav feedback, Eric S Fraga, 2013/01/17
Re: [O] org-caldav feedback, Christian Egli, 2013/01/21