emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Eric Luo <eric.wenbl@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: was this intentional with the default header ":results value"
Date: Sun, 15 Jul 2012 09:00:09 +0800	[thread overview]
Message-ID: <87d33xn8iu.fsf@gmail.com> (raw)
In-Reply-To: m1zk729tsw.fsf@tsdye.com

tsd@tsdye.com (Thomas S. Dye) writes:

Thanks, it's clear to me with the difference between "value" and
"output" now.

whether there is a way to tell emacs-lisp that "123456789123456789" is a
string rather than a number.

emacs-lisp handles the output as expected if the c1 has any character
other than numbers as the following.
,----
| #+BEGIN_SRC R
|   df <- data.frame(c1="c123456789123456789",c2=2)
|   df$c1 <- as.vector(df$c1)
|   df
| #+END_SRC
| 
| #+RESULTS:
| | c123456789123456789 | 2 |
| 
`----

> Aloha Eric,
>
> Eric Luo <eric.wenbl@gmail.com> writes:
>
>> Hi, 
>> Why in the following code block, c1 was printed as scientific notation
>> rather then characters.
>> ,----
>> | 
>> | #+BEGIN_SRC R :results value
>> |   df <- data.frame(c1="123456789123456789",c2=2)
>> | #+END_SRC
>> | 
>> | #+RESULTS:
>> | | 1.2345678912345678e+17 | 2 |
>> `----
>
> With :results value the results are passed from the source language into
> emacs-lisp and then displayed in the buffer.  So, the representation of
> things like very large numbers depends on how that was done in
> emacs-lisp, independent of the source language conventions.  In this
> case, I suspect the number was written with a formatting string and ‘%g’
> which uses scientific notation if that is a shorter representation.
>
>
>> But if the header :results output, the result was expected.
>> ,----
>> | 
>> | #+BEGIN_SRC R :results output 
>> |   df <- data.frame(c1="123456789123456789",c2=2)
>> |   df
>> | #+END_SRC
>> | 
>> | #+RESULTS:
>> | :                   c1 c2
>> | : 1 123456789123456789  2
>> `----
>>
>
> With :results output the results aren't translated into emacs-lisp.
> Instead, the output from the source language is collected and displayed
> in the buffer.  Thus, the output conventions of the source language are
> respected. 
>
> hth,

next prev parent reply	other threads:[~2012-07-15  1:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 14:24 was this intentional with the default header ":results value" Eric Luo
2012-07-14 16:44 ` Thomas S. Dye
2012-07-15  1:00   ` Eric Luo [this message]
2012-07-15  3:33     ` Thomas S. Dye
2012-07-15  3:54       ` Thomas S. Dye
2012-07-15  9:18         ` Eric Luo

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=87d33xn8iu.fsf@gmail.com \
    --to=eric.wenbl@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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

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