From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Bug in export of call lines
Date: Mon, 10 Mar 2014 13:16:09 +0100
Message-ID: <87ha768d12.fsf@gmail.com>
References: <m21tye69wk.fsf@tsdye.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40667)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1WMz7Z-000839-81
	for emacs-orgmode@gnu.org; Mon, 10 Mar 2014 08:15:59 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1WMz7S-00060u-Rw
	for emacs-orgmode@gnu.org; Mon, 10 Mar 2014 08:15:53 -0400
Received: from mail-we0-x231.google.com ([2a00:1450:400c:c03::231]:60685)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1WMz7S-00060Z-Ff
	for emacs-orgmode@gnu.org; Mon, 10 Mar 2014 08:15:46 -0400
Received: by mail-we0-f177.google.com with SMTP id u57so8233362wes.8
	for <emacs-orgmode@gnu.org>; Mon, 10 Mar 2014 05:15:45 -0700 (PDT)
In-Reply-To: <m21tye69wk.fsf@tsdye.com> (Thomas S. Dye's message of "Thu, 06
	Mar 2014 16:05:15 -1000")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>

Hello,

tsd@tsdye.com (Thomas S. Dye) writes:

> I've been dusting off a draft paper written when the new export
> framework was still in contrib. Now that I've brought the file
> up-to-date so that it exports asynchronously again, I'm getting an error
> that wasn't there before.

[...]

> Note the new line after each call result and the premature termination
> of the {description} environment.

It would help to see the source of "axe-x-section" and "axe-wt". Do they
insert spurious newline characters?

Also, you can call (org-export-execute-babel-code) to get what is really
parsed once Babel code is expanded.


Regards,

-- 
Nicolas Goaziou