From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [ANN] ASCII back-end for new export engine Date: Sun, 22 Jan 2012 16:45:11 +0100 Message-ID: <87zkdf3fnc.fsf@gmail.com> References: <87pqec4xua.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:51251) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RozdS-0001Om-HA for emacs-orgmode@gnu.org; Sun, 22 Jan 2012 10:47:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RozdR-00024f-9E for emacs-orgmode@gnu.org; Sun, 22 Jan 2012 10:47:14 -0500 Received: from mail-we0-f169.google.com ([74.125.82.169]:45543) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RozdR-00024X-38 for emacs-orgmode@gnu.org; Sun, 22 Jan 2012 10:47:13 -0500 Received: by werl4 with SMTP id l4so1878179wer.0 for ; Sun, 22 Jan 2012 07:47:12 -0800 (PST) In-Reply-To: (Martyn Jago's message of "Sun, 22 Jan 2012 14:43:52 +0000") 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: Martyn Jago Cc: emacs-orgmode@gnu.org Hello, Martyn Jago writes: > I've been playing with (org-export-dispatch) with regard to some simple > source blocks and have a couple of observations (apologies in advance if > source blocks are not fully implemented yet). > > The test code is: > > > * Test > > #+begin_src emacs-lisp # :exports both > ;; Add two numbers > (+ 2 3) > #+end_src > > #+results: > : 5 > > > 1) The commented out `# :exports both' appears to be exported as > uncommented and relevant (actually, this appears to be true of the > original exporter too). I cannot reproduce it. Anyway, see my comments below. > 2) If the source block is executed in buffer with (org-ctrl-c-ctrl-c), > as shown above, then the exporter appears to export the in-buffer > results /and/ the export-generated results (where :exports is results > or both) resulting in two sets of identical results in the export. It's out of exporter's scope. When you ask to export some buffer, what is really parsed is a copy of the current buffer with `org-export-blocks-preprocess' applied to it. So, simply apply that function in your test buffer, and you will see what is sent to the parser. That will explain why the results appear twice. In other words, tweaking the output of `org-export-blocks-preprocess' will automatically change the outcome of the export process. Regards, -- Nicolas Goaziou