From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: org-caldav: New version with proper two-way sync
Date: Wed, 16 Jan 2013 14:06:06 +1030 [thread overview]
Message-ID: <87bocp4x5l.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87bocr4ej2.fsf@engster.org> (David Engster's message of "Mon, 14 Jan 2013 22:53:53 +0100")
David Engster <deng@randomsample.de> writes:
> I just pushed a pretty big update to org-caldav. Get it at
>
> https://github.com/dengste/org-caldav
>
> The short story: org-caldav now does proper two-way
> syncing. It's pretty much a rewrite, actually. If you're already
> using org-caldav, you will have to start from scratch after
> updating.
David,
this is fantastic! I've just tried this out and it works
brilliantly, at least for org -> Google. I've not tried synching
yet but looking good so far. It's enough for me to stop using my
own system which did two way transfers but no synching.
I did have two sync errors. Is there any way to diagnose what
went wrong? The output from org-caldav is very nice in that it
provides a link to the entries that were processed, including
those with errors, but I cannot see anything strange in either of
the entries.
Off now to try two way synching!
Thanks for this,
eric
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-826-gbe0d87
next prev parent reply other threads:[~2013-01-16 3:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 21:53 org-caldav: New version with proper two-way sync David Engster
2013-01-14 22:29 ` Rasmus
2013-01-15 18:23 ` Vincent Beffara
2013-01-16 21:53 ` David Engster
2013-01-16 3:36 ` Eric S Fraga [this message]
2013-01-16 3:53 ` Eric S Fraga
2013-01-16 4:47 ` Eric S Fraga
2013-01-16 21:45 ` David Engster
2013-01-17 4:46 ` Eric S Fraga
2013-01-17 5:34 ` Eric S Fraga
2013-01-17 8:10 ` Detlef Steuer
2013-01-17 8:35 ` Eric S Fraga
2013-01-17 9:29 ` Detlef Steuer
2013-01-18 3:48 ` Eric S Fraga
2013-01-16 4:15 ` JBash
2013-01-16 9:47 ` Detlef Steuer
2013-01-16 21:35 ` David Engster
2013-01-17 8:12 ` Detlef Steuer
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=87bocp4x5l.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).