[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Bug in export of call lines
From: |
Nicolas Goaziou |
Subject: |
Re: [O] Bug in export of call lines |
Date: |
Mon, 10 Mar 2014 13:16:09 +0100 |
Hello,
address@hidden (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
- [O] Bug in export of call lines, Thomas S. Dye, 2014/03/06
- Re: [O] Bug in export of call lines,
Nicolas Goaziou <=
- Re: [O] Bug in export of call lines, Thomas S. Dye, 2014/03/10
- Re: [O] Bug in export of call lines, Eric Schulte, 2014/03/10
- Re: [O] Bug in export of call lines, Thomas S. Dye, 2014/03/10
- Re: [O] Bug in export of call lines, Eric Schulte, 2014/03/11
- Re: [O] Bug in export of call lines, Thomas S. Dye, 2014/03/11
- Re: [O] Bug in export of call lines, Eric Schulte, 2014/03/12
- Re: [O] Bug in export of call lines, Thomas S. Dye, 2014/03/12