emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Greg Tucker-Kellogg <gtuckerkellogg@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: R source block list export not working properly [7.8.11]
Date: Tue, 25 Sep 2012 05:28:36 -1000	[thread overview]
Message-ID: <m1ipb2m89n.fsf@tsdye.com> (raw)
In-Reply-To: <DDA639CB-6CA3-4350-A52D-5B768A919DEC@gmail.com> (Greg Tucker-Kellogg's message of "Tue, 25 Sep 2012 15:00:51 +0800")

Greg Tucker-Kellogg <gtuckerkellogg@gmail.com> writes:

> I reported this on the mailing list as a question, but it appears to be an
> actual bug, so I thought I should file it formally.  The following MWE
> shows the problem when trying to export an R character vector:
>
> #+begin_src R :exports results :results value list
> c("x","y","z")
> #+end_src
>
> #+RESULTS:
> - ("x")
> - ("y")
> - ("z")
>
> This is clearly not what is wanted, more or less ever.  What works,
> instead, requires R manipulation of the results, of the form:
>
> #+BEGIN_SRC R :exports results :results output raw
> a <- c("x","y","z")
> cat(paste("-", a), sep="\n")
> #+END_SRC
>
> #+RESULTS:
> - x
> - y
> - z
>
>
> Emacs  : GNU Emacs 24.2.1 (x86_64-apple-darwin, NS apple-appkit-1038.36)
> of 2012-08-27 on bob.porkrind.org
> Package: Org-mode version 7.8.11

Hi Greg,

The problem is that no one is maintaining ob-r.el.  The author, Dan
Davison, has moved on to other things.

Eric Schulte will apply patches to ob-r.el.  Perhaps you could suggest a
patch that would fix this behavior?

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2012-09-25 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  7:00 Bug: R source block list export not working properly [7.8.11] Greg Tucker-Kellogg
2012-09-25 15:28 ` Thomas S. Dye [this message]
2012-09-26  0:38   ` Greg Tucker-Kellogg

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=m1ipb2m89n.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gtuckerkellogg@gmail.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).