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: Fri, 1 Mar 2013 16:37:51 +0100	[thread overview]
Message-ID: <CAPaq-gPJoiaWfwXxq7M_WrTwYgyHrE5sNYqDW3eCKG=ndZAxaw@mail.gmail.com> (raw)
In-Reply-To: <87boc2ln91.fsf@engster.org>

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

Hi David,


On 2 February 2013 17:00, David Engster <deng@randomsample.de> wrote:

> I pushed a change which should correctly deal with timestamps inside the
> header line. Please let me know if this works for you.
>

Sorry for the long delay to your patch.
First I thought its working perfect.
However, I noticed the following small glitch. I think its a minor problem.
Syncing back from caldav to org creates the following.

Original in org-mode

TODO Neuer Termin mit Foo und Bar <2013-03-06 Wed 10:00-10:00>
    :PROPERTIES:
    :ID:       8a9651c0-faee-4416-afa6-979e328a3d15
    :END:

Synching to caldav work flawless
In SOGo I can find

TODO Neuer Termin mit Foo und Bar
*Please note there is a space at the end of the line. Not sure if this
might trouble*

Now I make a tiny change e.g. change the length of the appointment from
within SOGo and sync back I get

TODO TODO Neuer Termin mit Foo und Bar r<2013-03-06 Wed 10:00-11:00>
    :PROPERTIES:
    :ID:       8a9651c0-faee-4416-afa6-979e328a3d15
    :END:

As you can see the TODO doubled and the last character of the title is
repeated.

I guess its simply some regexp, which needs some finetuning.

All the best and thanks a lot

Torsten

CC. Did you had a chance to look into calfw and think about how to make use
of it for org-caldav?

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

  reply	other threads:[~2013-03-01 15:37 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
2013-01-23 20:16                 ` David Engster
2013-02-02 16:00                 ` David Engster
2013-03-01 15:37                   ` Torsten Wagner [this message]
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-gPJoiaWfwXxq7M_WrTwYgyHrE5sNYqDW3eCKG=ndZAxaw@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).