emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Torsten Wagner <torsten.wagner@gmail.com>
To: Torsten Wagner <torsten.wagner@gmail.com>,
	Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: org-caldav feedback
Date: Wed, 23 Jan 2013 15:38:10 +0100	[thread overview]
Message-ID: <CAPaq-gMv=HkWjE==3=HhOiYPOiLuKOYaZkpzjuJ9JPU2q76i_w@mail.gmail.com> (raw)
In-Reply-To: <87boch2dik.fsf@engster.org>

[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 2475 bytes --]

next prev parent reply	other threads:[~2013-01-23 14:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 15:32 org-caldav feedback Torsten Wagner
2013-01-17 19:05 ` David Engster
2013-01-17 21:28   ` Torsten Wagner
2013-01-21 19:29     ` David Engster
2013-01-21 16:28   ` Torsten Wagner
2013-01-21 19:25     ` David Engster
2013-01-21 19:37       ` Torsten Wagner
2013-01-21 21:32         ` David Engster
2013-01-22 15:35           ` Torsten Wagner
2013-01-22 20:01             ` David Engster
2013-01-23  6:00               ` Eric S Fraga
2013-01-23 14:22                 ` Torsten Wagner
2013-01-23 20:11                   ` David Engster
2013-01-24  0:37                   ` Eric S Fraga
2013-01-23 20:23                 ` David Engster
2013-01-24  0:38                   ` Eric S Fraga
2013-01-23 14:38               ` Torsten Wagner [this message]
2013-01-23 20:16                 ` David Engster
2013-02-02 16:00                 ` David Engster
2013-03-01 15:37                   ` Torsten Wagner
2013-03-02 14:08                     ` David Engster
2013-01-18  3:47 ` Eric S Fraga
2013-01-21  9:38 ` Christian Egli

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='CAPaq-gMv=HkWjE==3=HhOiYPOiLuKOYaZkpzjuJ9JPU2q76i_w@mail.gmail.com' \
    --to=torsten.wagner@gmail.com \
    --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

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).