emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [org-babel R] Difference between output in RStudio and in Org Babel
Date: Wed, 10 Dec 2014 16:36:18 -0500	[thread overview]
Message-ID: <87oarb427h.fsf@gmail.com> (raw)
In-Reply-To: <86y4qfgqzr.fsf_-_@example.com>

Hi Seb,

[re-adding the list to cc]

2014ko abenudak 10an, Sebastien Vauban-ek idatzi zuen:
> FYI, the link is a screen capture image, in this case, not a video!

OK, now I feel sheepish.  I assumed from the screencast.com URL that
there was intended to be some video, for which the image displayed was
just the (first/last/etc.) frame.  Now I understand better.

> With my example, what I expect is:
>  |     | liste          | nb |
>  |-----+----------------+----|
>  | abc | item31\nitem80 |  2 |
>  | def | item52         |  1 |

There’s no convention in org tables that “\n” (i.e. two characters,
backslash + n) means newline (i.e. one character).

> In this case, I'd expect the same as in RStudio; that is, no multi-line
> cell, but simply a cell with a string in it -- which, yes, does contain
> the \n character:

What R’s console shows you (either RStudio or vanilla R) is a “human
readable” representation of the data frame, which includes doing
things like changing the newline character into a \n escape sequence
(and other stuff, like padding the columns with spaces so they all
line up vertically).  But when Org communicates with R, it asks for a
machine-readable version, which doesn’t include such niceties.  When
that machine-readable version includes a newline character in a data
field (as your example table does), org doesn’t know what to do and
messes up.

Aaron Ecay

      parent reply	other threads:[~2014-12-10 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 15:04 [org-babel R] Difference between output in RStudio and in Org Babel Sebastien Vauban
     [not found] ` <87r3w7462j.fsf@gmail.com>
     [not found]   ` <86y4qfgqzr.fsf_-_@example.com>
2014-12-10 21:36     ` Aaron Ecay [this message]

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:

  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=87oarb427h.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sva-news@mygooglest.com \


* 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


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).