emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Bug in export of call lines
Date: Mon, 10 Mar 2014 13:16:09 +0100	[thread overview]
Message-ID: <87ha768d12.fsf@gmail.com> (raw)
In-Reply-To: <m21tye69wk.fsf@tsdye.com> (Thomas S. Dye's message of "Thu, 06 Mar 2014 16:05:15 -1000")

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

  reply	other threads:[~2014-03-10 12:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  2:05 Bug in export of call lines Thomas S. Dye
2014-03-10 12:16 ` Nicolas Goaziou [this message]
2014-03-10 17:14   ` Thomas S. Dye
2014-03-10 17:38     ` Eric Schulte
2014-03-11  2:45       ` Thomas S. Dye
2014-03-11 13:23         ` Eric Schulte
2014-03-11 21:50           ` Thomas S. Dye
2014-03-12  1:40             ` Eric Schulte
2014-03-12  6:00               ` Thomas S. Dye

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ha768d12.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).