From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Engster Subject: Re: org-caldav can't find org-prepare-agenda-buffers Date: Wed, 27 Feb 2013 20:18:54 +0100 Message-ID: <87vc9d36qp.fsf@engster.org> References: <87k3puyri0.fsf@free.fr> <871uc1sv4s.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:57483) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UAmX9-0004xa-Ov for emacs-orgmode@gnu.org; Wed, 27 Feb 2013 14:19:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UAmWx-00072F-Dm for emacs-orgmode@gnu.org; Wed, 27 Feb 2013 14:19:14 -0500 Received: from randomsample.de ([83.169.19.17]:41205) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UAmWw-0006yU-17 for emacs-orgmode@gnu.org; Wed, 27 Feb 2013 14:19:07 -0500 In-Reply-To: <871uc1sv4s.fsf@bzg.ath.cx> (Bastien's message of "Wed, 27 Feb 2013 15:12:51 +0100") 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: Bastien Cc: emacs-orgmode@gnu.org, Julien Cubizolles Bastien writes: > Hi Julien, > > Julien Cubizolles writes: > >> As of today, org-cadav-syn fails with >> >> org-export-icalendar: Symbol's function definition is void: >> org-prepare-agenda-buffers >> >> Actually, I can't find this function but org-agenda-prepare-buffers >> exist. Are there two different functions or is there a confusion >> somewhere=A0? > > The function has been renamed a while ago. > > `org-agenda-prepare-buffers' is the correct name. org-caldav does not call this function. It however requires org-icalendar, and that was renamed to ox-icalendar in org git. So I guess it pulls org-icalendar from the Org that is included with Emacs, which calls the obsoleted function. I don't follow org-development very closely. I realize there's a new exporter, but renaming the exporters in this way is asking for trouble. In this case, we've actually been lucky that an error like the above is thrown; much more subtle things can happen when new and old Org functions interact. -David