From: Eric Schulte <schulte.eric@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Bug in export of call lines
Date: Mon, 10 Mar 2014 11:38:05 -0600 [thread overview]
Message-ID: <87k3c2vts2.fsf@gmail.com> (raw)
In-Reply-To: <m238iqou1m.fsf@tsdye.com> (Thomas S. Dye's message of "Mon, 10 Mar 2014 07:14:13 -1000")
tsd@tsdye.com (Thomas S. Dye) writes:
> Aloha Nicolas,
>
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> 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.
>
> That's a big help. Thanks.
>
> It appears that executing the R code block does insert a newline. This
> must be the behavior that changed.
>
> executing R code block (axe-x-section)...
> Wrote /var/folders/fp/mgkcqpy17clb6dzh3_xgs0n80000gn/T/babel-78240Cke/ob-input-78240NlJ
> "3.7 \\texttimes 2
> "
> executing Emacs-Lisp code block...
>
> (results (quote "3.7 \\texttimes 2
> "))
>
> Here is the source code:
>
> *** Cross-section of a particular tool, in cm
> #+name: axe-x-section
> #+header: :var t=final-axe-table
> #+header: :var a="3141"
> #+header: :results raw
> #+BEGIN_SRC R
> w <- t[t[,2]==a,16]/10
> th <- t[t[,2]==a,18]/10
> paste0(w, '\\texttimes', th)
> #+END_SRC
> #+results: axe-x-section
> 3.9\texttimes2
>
I believe this issue of newlines returned from inline code blocks
(specifically with R) came up on the list recently, but unfortunately I
can't find the conversation.
Somehow this doesn't seem to be a problem with other languages, so I
believe the necessary fix may be R specific.
Sorry I can't be of more help,
>
> All the best,
> Tom
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2014-03-10 17:40 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
2014-03-10 17:14 ` Thomas S. Dye
2014-03-10 17:38 ` Eric Schulte [this message]
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=87k3c2vts2.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--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).