From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: [ANN] ASCII back-end for new export engine Date: Mon, 23 Jan 2012 13:05:52 -0700 Message-ID: <87ehuqqj4v.fsf@gmx.com> References: <87pqec4xua.fsf@gmail.com> <87zkdf3fnc.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:40513) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RpQ9O-0003Bp-2V for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 15:05:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RpQ9M-0000EJ-UX for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 15:05:58 -0500 Received: from mailout-us.gmx.com ([74.208.5.67]:58048) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RpQ9M-0000EF-Iy for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 15:05:56 -0500 In-Reply-To: <87zkdf3fnc.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 22 Jan 2012 16:45:11 +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: Nicolas Goaziou Cc: Martyn Jago , emacs-orgmode@gnu.org >> 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. I disagree. The current exporter conforms to the value of the :results header argument (e.g., silent, replace, append, etc...) when executing code blocks during export. I see no reason why the new exporter should not as well. > 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. > Hmm, in light of this description it seems that the new export /should/ have the same behavior WRT code block execution as the current exporter. If not I wonder if a complete minimal example could be provided. Thanks, > > > Regards, -- Eric Schulte http://cs.unm.edu/~eschulte/