Re: [O] org-babel R, export, and :result value raw

[Eric Schulte]

Hi Christophe,

This issue of result wrappers (e.g., raw org html) not playing well with
result types (e.g., vector, scalar) came up a couple of months ago on
this mailing list and was not resolved.

I've just pushed up a change which should fix this problem, along with
an R-specific fix so that R respects the "scalar" and "verbatim"
:results header arguments so that the following now works.

#+begin_src R :results raw scalar
"[[file:bar.png]]"
#+end_src

Best -- Eric

Christophe Rhodes <address@hidden> writes:

> Hi,
>
> Consider the following org-mode file, assuming that org-babel support
> for emacs lisp and R is active:
>
> --- begin ---
> #+TITLE: Foo
>
> #+begin_src emacs-lisp :exports results :results value raw
> "[[file:foo.png]]"
> #+end_src
>
> #+results:
> [[foo.png]]
>
> #+begin_src R :exports results :results value raw
> "[[file:bar.png]]"
> #+end_src
> #+results: 
> [[file:bar\.png]]
> ---  end  ---
>
> The problem is probably obvious from the above, but to be explicit: the
> intent is to generate raw org-mode from the code blocks (this case is
> hugely simplified from my actual application), producing links to images
> which will then be part of the eventual exported document.  For emacs
> lisp, this works fine; for R, the path through files and specifically
> org-babel-import-elisp-from-file / org-babel-string-read causes the
> return value to be misinterpreted, introducing an extra backslash, and
> therefore generating bogus export files.
>
> (This used to work for my use case in org-mode 7.4, and does not work in
> org-mode 7.6; I looked at HEAD to see if I could identify a fix, but did
> not find one -- I'm sorry if I missed it)
>
> Thanks,
>
> Christophe
>
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/