From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: How are people handling their calendars? Date: Mon, 24 Oct 2016 08:07:14 +0200 Message-ID: <87y41e7019.fsf@ericabrahamsen.net> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52811) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1byYQZ-0008F6-EG for emacs-orgmode@gnu.org; Mon, 24 Oct 2016 02:08:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1byYQW-0007GW-4L for emacs-orgmode@gnu.org; Mon, 24 Oct 2016 02:08:07 -0400 Received: from [195.159.176.226] (port=37837 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1byYQV-0007GS-UK for emacs-orgmode@gnu.org; Mon, 24 Oct 2016 02:08:04 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1byYQ5-0007ED-IP for emacs-orgmode@gnu.org; Mon, 24 Oct 2016 08:07:37 +0200 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" To: emacs-orgmode@gnu.org Tristan Strange writes: > The world of calendars is a murky one isn't it? After a couple of > weeks of fiddling around I finally decided I'd keep my TODO's, > deadlines, etc in a TODO.org and have org-gcal fetch (note not > synchronise) my calendar from Google. > > That way I do all my daily TODO mangling in orgmode, edit calendar > when on Desktop or Mobile and pull results in to org agenda for easier > viewing. > > So how do you lot handle your calendars? > > Do any of you have a working two way set up with CalDAV or anything? I use the org-caldav package, and that works quite well for two-way sync. You can use sync multiple calendars, selecting by tags, etc. The only trouble I had was using a radicale server, which seemed to expose a bug in xml.el. That's bug 23440, which has a patch that fixes the problem. The patch hasn't actually been integrated into Emacs, but I suppose will eventually.