From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: new exporter Date: Thu, 28 Jun 2012 09:03:25 +0200 Message-ID: <87pq8j2a0y.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> <87k3yu15wj.fsf@gmail.com> <87395hkj7u.fsf@Rainer.invalid> <87fw9gwmet.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34375) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sk8oR-0001lu-Uc for emacs-orgmode@gnu.org; Thu, 28 Jun 2012 03:06:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sk8oQ-0005HK-0M for emacs-orgmode@gnu.org; Thu, 28 Jun 2012 03:06:47 -0400 Received: from mail-wi0-f171.google.com ([209.85.212.171]:64632) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sk8oP-0005GF-O6 for emacs-orgmode@gnu.org; Thu, 28 Jun 2012 03:06:45 -0400 Received: by wibhq4 with SMTP id hq4so4453901wib.12 for ; Thu, 28 Jun 2012 00:06:43 -0700 (PDT) In-Reply-To: <87fw9gwmet.fsf@Rainer.invalid> (Achim Gratz's message of "Wed, 27 Jun 2012 22:05:30 +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: > This code snippet has at last after revealed where the problem is: the > function call to (current-buffer) gets unquoted, when it clearly needs > to be in the expansion. The literal expansion of the buffer content > into the compiled bytecode is similarly explained by an unquoting of > (buffer-string). Here's a patch that seems to fix the compilation > (without changelog and everything because I think you may want to check > the rest of the new exporters for similar constructs). Nice catch. I think you can go ahead and commit it: your description of the problem will be more accurate than mine. Thank you for this investigation and, obviously, for the fix. Regards, -- Nicolas Goaziou