From mboxrd@z Thu Jan 1 00:00:00 1970 From: Torsten Wagner Subject: Re: org-caldav feedback Date: Wed, 23 Jan 2013 15:22:34 +0100 Message-ID: References: <87wqvb1vh4.fsf@engster.org> <87obgi2v9t.fsf@engster.org> <87fw1u2pdp.fsf@engster.org> <87boch2dik.fsf@engster.org> <8738xsa16n.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b2ed947ea49f904d3f56c7b Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59532) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ty1Dv-0006qX-5H for emacs-orgmode@gnu.org; Wed, 23 Jan 2013 09:22:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ty1Do-0003sf-Hu for emacs-orgmode@gnu.org; Wed, 23 Jan 2013 09:22:43 -0500 Received: from mail-da0-f49.google.com ([209.85.210.49]:57438) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ty1Do-0003sV-8u for emacs-orgmode@gnu.org; Wed, 23 Jan 2013 09:22:36 -0500 Received: by mail-da0-f49.google.com with SMTP id v40so3833288dad.36 for ; Wed, 23 Jan 2013 06:22:34 -0800 (PST) In-Reply-To: <8738xsa16n.fsf@ucl.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode Mailing List --047d7b2ed947ea49f904d3f56c7b Content-Type: text/plain; charset=ISO-8859-1 Hi Eric, If I understood David right, the "UTC" option is just an addition to the already present options. Thus, if you used e.g. "Europe/Berlin" before, you do not need to change anything and in fact, you shouldn't see a difference. However, if you face time shifts between org and the caldav calendar you might try "UTC". Hope that helps Torsten On 23 January 2013 07:00, Eric S Fraga wrote: > David Engster writes: > > [...] > > > I think I found a better solution. I pushed a change to org-caldav which > > allows to set org-icalendar-timezone to the string "UTC", which will put > > events using universal time. The server should then transpose it to the > > timezone you have set in your SOGo preferences. It works for me (for > > SOGo, mind you; other calendar servers don't work well with that). > > David, > > for those of us not using SOGo (I use Google), what should we do? I've > not updated the version of org-caldav I'm using yet. > > By the way, I will take this opportunity to say that org-caldav is > working like a charm for me. Although I haven't really pushed it to the > limits, for day to day stuff it's working very well. I've had to clear > out the org-caldav-xxx.el file in .emacs.d a couple of times but that's > typically due to my doing things on the same entry in both calendar > systems (org and Google). However, clearing out the file and having > org-caldav re-sync everything from scratch is a simple and good enough > solution for when problems arise. > > Thanks again, > eric > > -- > : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D > : in Emacs 24.3.50.1 and Org release_7.9.3d-837-ge37613 > > > --047d7b2ed947ea49f904d3f56c7b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Eric,

If I understood David right, the "UTC"= ; option is just an=A0addition=A0to the already present options.
= Thus, if you used e.g. "Europe/Berlin" before, you do not need to= change anything and in fact, you shouldn't see a difference.
However, if you face time shifts between org and the caldav calendar y= ou might try "UTC".

Hope that helps

Torsten

On 23 Januar= y 2013 07:00, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
David Engster <deng@randomsample.de> writes:

[...]

> I think I found a better solution. I pushed a change to org-caldav whi= ch
> allows to set org-icalendar-timezone to the string "UTC", wh= ich will put
> events using universal time. The server should then transpose it to th= e
> timezone you have set in your SOGo preferences. It works for me (for > SOGo, mind you; other calendar servers don't work well with that).=

David,

for those of us not using SOGo (I use Google), what should we do? =A0I'= ve
not updated the version of org-caldav I'm using yet.

By the way, I will take this opportunity to say that org-caldav is
working like a charm for me. =A0Although I haven't really pushed it to = the
limits, for day to day stuff it's working very well. =A0I've had to= clear
out the org-caldav-xxx.el file in .emacs.d a couple of times but that's=
typically due to my doing things on the same entry in both calendar
systems (org and Google). =A0However, clearing out the file and having
org-caldav re-sync everything from scratch is a simple and good enough
solution for when problems arise.

Thanks again,
eric

--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-837-ge37613



--047d7b2ed947ea49f904d3f56c7b--