From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Riedy Subject: org-caldav for Google or Zimbra? Date: Tue, 24 Sep 2013 17:27:04 -0400 Message-ID: <871u4dsyfr.fsf@qNaN.sparse.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45370) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VOaGH-0006BZ-2X for emacs-orgmode@gnu.org; Tue, 24 Sep 2013 17:35:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VOaG9-0001xj-OP for emacs-orgmode@gnu.org; Tue, 24 Sep 2013 17:35:12 -0400 Received: from plane.gmane.org ([80.91.229.3]:59813) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VOaG9-0001tn-IZ for emacs-orgmode@gnu.org; Tue, 24 Sep 2013 17:35:05 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VOaG8-0001qG-8G for emacs-orgmode@gnu.org; Tue, 24 Sep 2013 23:35:04 +0200 Received: from lawn-128-61-56-129.lawn.gatech.edu ([128.61.56.129]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Sep 2013 23:35:04 +0200 Received: from jason by lawn-128-61-56-129.lawn.gatech.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Sep 2013 23:35:04 +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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Cc: David Engster Does anyone have org-caldav working with the new Google endpoint or Zimbra? The former errors out (there's an issue on github, but I don't want a github account to ask there), and the latter uses a different URL scheme... Zimbra's URL scheme is https://server.example.com/dav/username/calendarname with a calendarname is Calendar. Special-casing org-caldav-events-url for my server appears to work. Feels like that function could be over-ridden per server / target org file, but I'm not quite sure what the right granularity should be. Hm. Perhaps having each synced calendar in a separate org file might work. Each org file could set some file-wide parameters like calendar URL. -- Jason, who no longer has relevant papers on file...