From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Bug in export of call lines Date: Mon, 10 Mar 2014 11:38:05 -0600 Message-ID: <87k3c2vts2.fsf@gmail.com> References: <87ha768d12.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36174) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WN4BR-0004cc-Nb for emacs-orgmode@gnu.org; Mon, 10 Mar 2014 13:40:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WN4BM-00081B-Va for emacs-orgmode@gnu.org; Mon, 10 Mar 2014 13:40:13 -0400 Received: from mail-pb0-x22e.google.com ([2607:f8b0:400e:c01::22e]:46784) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WN4BM-00080r-PU for emacs-orgmode@gnu.org; Mon, 10 Mar 2014 13:40:08 -0400 Received: by mail-pb0-f46.google.com with SMTP id rq2so7510335pbb.19 for ; Mon, 10 Mar 2014 10:40:05 -0700 (PDT) In-Reply-To: (Thomas S. Dye's message of "Mon, 10 Mar 2014 07:14:13 -1000") 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: "Thomas S. Dye" Cc: Org-mode , Nicolas Goaziou tsd@tsdye.com (Thomas S. Dye) writes: > Aloha Nicolas, > > Nicolas Goaziou 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/o= b-input-78240NlJ > "3.7=C2=A0\\texttimes=C2=A02 > " > executing Emacs-Lisp code block... > > (results (quote "3.7=C2=A0\\texttimes=C2=A02 > ")) > > Here is the source code: > > *** Cross-section of a particular tool, in cm > #+name: axe-x-section > #+header: :var t=3Dfinal-axe-table > #+header: :var a=3D"3141" > #+header: :results raw > #+BEGIN_SRC R > w <- t[t[,2]=3D=3Da,16]/10 > th <- t[t[,2]=3D=3Da,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 --=20 Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D