From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: Orgmodeorg-export-generic gives an error Date: Thu, 23 Jul 2009 09:33:36 +0200 Message-ID: <87eis76egf.fsf@bzg.ath.cx> References: <87eisgjl8s.fsf@bzg.ath.cx> <211769420907171223r6ffe0086mccfbed65aa0fe3f5@mail.gmail.com> <877hy137vz.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MTsoL-0006zA-Ax for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 03:33:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MTsoF-0006up-Un for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 03:33:52 -0400 Received: from [199.232.76.173] (port=39883 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MTsoF-0006uB-EU for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 03:33:47 -0400 Received: from mx20.gnu.org ([199.232.41.8]:22580) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MTsoE-0004bq-WA for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 03:33:47 -0400 Received: from wf-out-1314.google.com ([209.85.200.170]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MTsoE-0005FY-CA for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 03:33:46 -0400 Received: by wf-out-1314.google.com with SMTP id 23so217886wfg.24 for ; Thu, 23 Jul 2009 00:33:45 -0700 (PDT) In-Reply-To: (Shelagh Manton's message of "Wed, 22 Jul 2009 23:33:17 +0000 (UTC)") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Shelagh Manton Cc: emacs-orgmode@gnu.org Shelagh Manton writes: > On Wed, 22 Jul 2009 08:13:53 -0700, Wes Hardaker wrote: > >>>>>>> On Wed, 22 Jul 2009 01:59:12 +0200, Bastien >>>>>>> said: >> >> B> Those two functions come from alist.el which is included in Apel: >> >> So does that mean it's safe to leave the functions in use within >> org-export generic, or should I replace it with a locally defined >> slightly-different-named version? > > Perhaps just putting (require 'alist) in your file will be enough. Yes. Or maybe check whether this feature is available or not with (featurep 'alist), use it if it is, implement it if it's not. -- Bastien