From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: new exporter Date: Tue, 26 Jun 2012 16:53:16 +0200 Message-ID: <87k3yu15wj.fsf@gmail.com> References: <3C38420E-E2FA-4CAB-B3FD-9C5F8584E60A@gmail.com> <81fwadrgoo.fsf@gmail.com> <87396dzlai.fsf_-_@Rainer.invalid> <871ulqgb4t.fsf@gmail.com> <87y5nyx4ku.fsf@Rainer.invalid> <87a9zq7htj.fsf@Rainer.invalid> <87r4t261fw.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54791) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjXC7-0003IP-7B for emacs-orgmode@gnu.org; Tue, 26 Jun 2012 10:56:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SjXC2-0003Pq-9w for emacs-orgmode@gnu.org; Tue, 26 Jun 2012 10:56:42 -0400 Received: from mail-wi0-f171.google.com ([209.85.212.171]:56590) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjXC2-0003Ni-1u for emacs-orgmode@gnu.org; Tue, 26 Jun 2012 10:56:38 -0400 Received: by wibhq4 with SMTP id hq4so3076347wib.12 for ; Tue, 26 Jun 2012 07:56:34 -0700 (PDT) In-Reply-To: <87r4t261fw.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 26 Jun 2012 08:18:27 +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: Achim Gratz Cc: emacs-orgmode@gnu.org Hello, Achim Gratz writes: > Achim Gratz writes: >> This causes the (current-buffer) to expand literally into the byte-code >> (look at the byte-code!) instead of being compiled as a function, which >> obviously isn't going to work. This does not happen if I either remove >> the cond form or if I wrap the BODY in save-restriction in progn, but I >> haven't done any further investigation if the code still works with that >> change and if maybe there are other places that are similarly struck. > > No, that's not right... as long as I compile org-export.el in isolation, > it compiles correctly. It croaks if I compile either one of > org-e-html.el or org-e-odt.el in the same session. These are the two > backends that have a (require 'org-export) in them. Speaking about that, as you suggested already, we should move, temporarily, the dispatcher into another file (i.e. org-e-extra.el) which would require everything (org-element, org-export, org-e-publish, org-e-latex,...) and have _every_ back-end require org-export and org-element only. That may not solve the problem, but could at least simplify it. Is that fine? Regards, -- Nicolas Goaziou