From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: David Engster <deng@randomsample.de>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-caldav: New version with proper two-way sync
Date: Wed, 16 Jan 2013 15:17:10 +1030 [thread overview]
Message-ID: <8738y14tv5.fsf@ucl.ac.uk> (raw)
In-Reply-To: <877gnd4wcv.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 16 Jan 2013 14:23:20 +1030")
David,
I'm following up on my own posts... how uncool! ;-)
I've tracked down the root of the various problems I have
encountered with the synchronisation. It all comes down to
character sets. I have some entries that have UTF-8 characters
that are not present in ASCII, specifically accented characters
and similar (latin1, basically, but not exclusively). Any such
entries cause the synchronisation to fail.
Resuming a failed synchronisation seems to forget to try to bring
in the external calendar entries into org? In other words,
resuming doesn't really resume but seems to start at some later
point. Not sure.
In any case, temporarily, I have commented out the problem entries
from my org agenda files and everything now works very well
indeed, including two way synchronisation of creating, deleting
and changing.
The fact that descriptions are not synchronised for changed
entries is something I understand but probably need to think about
some more (in terms of default behaviour). Is there a practical
limitation on the size of the description entry that could be
synchronised? The default is 100 but would there be any harm in
having this 1, 2 or even 3 orders of magnitude larger? Or even
unlimited? Just wondering.
Anyway, with respect to my problems, would you please have a look
to see if you are assuming ASCII or similar and whether there is
anything you can do about this? I (and many others, I assume)
really do need to be able to work in UTF-8 at the very least. I
am hooked on org-caldav already and would hate to have to go back
to my old system!
Thanks again,
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 4:46 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
2013-01-16 3:53 ` Eric S Fraga
2013-01-16 4:47 ` Eric S Fraga [this message]
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=8738y14tv5.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=deng@randomsample.de \
--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).