emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <davison@stats.ox.ac.uk>
To: "Weiss, Bernd " <bernd.weiss@uni-koeln.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Problems sourcing R code
Date: Sun, 08 Nov 2009 14:05:27 -0500	[thread overview]
Message-ID: <877hu0vnuw.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <4AF5CFB8.3020000@uni-koeln.de> (Bernd Weiss's message of "Sat, 07 Nov 2009 20:51:20 +0100")

"Weiss, Bernd " <bernd.weiss@uni-koeln.de> writes:

> Dear all,
>
> I am having trouble sourcing R code from within an org-file via
> org-babel, i.e. I cant' replicate the most simple examples
>
> #+begin_src R :results value
> matrix(rnorm(6), nrow=2)
> #+end_src
>
> That's the error message I get whenever I type in C-c C-c:
>
> "executing R source code block...
> Die Syntax für den Dateinamen, Verzeichnisnamen oder die
> Datenträgerbezeichnung ist falsch.
> No result returned by source block"

Dear Bernd,

This is a problem relating to running R as an external shell process
under Windows. For the time-being, please use the :session header
argument to specify that evaluation is to take place in a persistent
emacs R session. Alternatively, you could use the following
configuration code to force R blocks to always use the specified session
(you can change the session name of course):

(setq org-babel-default-header-args:R '((:session . "*my-R-session*")))

Session-based evaluation is described briefly at

http://orgmode.org/worg/org-contrib/babel/org-babel.php#basic-functionality

Thanks for the report. We will investigate the issues with running R as
an external process under Windows.

Best wishes,

Dan

>
>
> However, I am not having any problems with the shell-example
>
> #+begin_src sh
>   echo "This file takes up `du -h org-babel.org |sed 's/\([0-9k]*\)[
> ]*org-babel.org/\1/'`"
> #+end_src
>
> Org-R works as expected, i.e. I can source the following example without
> any problems
>
> #+RR: x <- c(rnorm(10, mean=-3, sd=1), rnorm(10, mean=3, sd=1))
> #+R: title:"continuous-data" output-to-buffer:t
>
>
> My setup:
> - MS-Win Vista
> - GNU Emacs 23.1.1 (i386-mingw-nt6.0.6002) of 2009-07-30 on SOFT-MJASON
> - Org-mode: Org-mode version 6.32trans (release_6.32b.127.g471c2);
> - ESS: v5.5
> - my .emacs/_emacs-File: <http://metaanalyse.de/tmp/_emacs>
>
>
> Thanks in advance for your help
>
> Bernd
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-11-08 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-07 19:51 [babel] Problems sourcing R code Weiss, Bernd 
2009-11-08 19:05 ` Dan Davison [this message]
2009-11-08 19:54   ` Weiss, Bernd 

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=877hu0vnuw.fsf@stats.ox.ac.uk \
    --to=davison@stats.ox.ac.uk \
    --cc=bernd.weiss@uni-koeln.de \
    --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
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).