From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: org-caldav can't find org-prepare-agenda-buffers Date: Thu, 28 Feb 2013 08:38:31 +0100 Message-ID: <87621cj3bc.fsf@bzg.ath.cx> References: <87k3puyri0.fsf@free.fr> <871uc1sv4s.fsf@bzg.ath.cx> <87vc9d36qp.fsf@engster.org> <87lia9o0e9.fsf@bzg.ath.cx> <878v692ae0.fsf@engster.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43240) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UAy4Y-0002Y6-RS for emacs-orgmode@gnu.org; Thu, 28 Feb 2013 02:38:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UAy4X-0003iY-PH for emacs-orgmode@gnu.org; Thu, 28 Feb 2013 02:38:34 -0500 Received: from mail-wi0-f175.google.com ([209.85.212.175]:65497) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UAy4X-0003iR-IX for emacs-orgmode@gnu.org; Thu, 28 Feb 2013 02:38:33 -0500 Received: by mail-wi0-f175.google.com with SMTP id l13so7325478wie.8 for ; Wed, 27 Feb 2013 23:38:32 -0800 (PST) In-Reply-To: <878v692ae0.fsf@engster.org> (David Engster's message of "Thu, 28 Feb 2013 07:57:43 +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: David Engster Cc: emacs-orgmode@gnu.org, Julien Cubizolles Hi David, David Engster writes: > Of course I can fix this. But I hope you realize that any third-party > code out there that requires an exporter will load the old one from > Emacs proper. Yes, I'm well aware of this. The change now lives in the master branch, and will happen when we release 8.0, hopefully in a not so distant future. We will document all incompatible changes in the release notes, as we usually do. I expect third-party maintainers to read these notes. > I'm wondering why you felt the need to rename them. If the > new exporters are compatible with the old ones, why not keep the names? > This would also avoid that the provided feature differs from the used > name prefix (ox-icalendar != org-icalendar). There are several good reasons for this: 1) conflicting library names: we now have org-man.el (for links to man pages) and ox-man.el (for exporting); 2) using the dedicated prefix ox- makes it clear that the library is an export backend, the same way that the ob- prefix makes it clear it is to support a language for Org Babel. In general, the change is incompatible for third-part libraries by is clearly useful for future maintainance, so the trade-off was in favor of making it, and 8.0 is a good time for it. Best, -- Bastien