Christopher W. Ryan <cr...@binghamton.edu> wrote: > John and Nick-- > > The question about whether I have python on my machine is not silly--I > am. Got so carried away I forgot I was on my work computer, which indeed > does not have python. But I do have R and perl, and similar code blocks > in either language yield the same problem, so I'll just focus on them as > examples (he said, sheepishly.) > > I usually interface with R via emacs ESS. Currently ESS is using R > version 2.11.1. > > R executable is in C:\Program Files\R\R-2.11.1\bin > > I usually interface with perl via another text editor, Programmer's > Notepad, set up with drop-down menu item to execute the file in perl. > > Perl executable is in C:\strawberry\perl\bin > > C:\Org\org-7.7\lisp contains, among others, files called ob-R.el and > ob-perl.el > > Currently my path variable looks like this: > > Files\QuickTime\QTSystem\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Xpdf;C:\strawberry\perl\bin;C:\strawberry\c\bin;C:\strawberry\perl\site\bin > > > My .emacs now contains: > > ;; active Babel languages > (org-babel-do-load-languages > 'org-babel-load-languages > '((R . t) > (python . t) > (perl . t) > )) > > > As to Nick's questions, > > M-x locate-library RET ob-R RET > > tells me ob-R is located in C:\Org\org-7.7\lisp\ob-R.el > > M-: to evaluate (require 'ob-R.el) > > yields ob-R in the minibuffer > > Then C-c C-c in the R code block yields > > Code block produced not output. > > in the minibuffer, > > and a new buffer that says, > > 'R' is not recognized as an internal or external command, > operable program or batch file. >
It's probably a path issue as you surmise below. ob-R.el includes the following: (defvar org-babel-R-command "R --slave --no-save" "Name of command to use for executing R code.") Try setting something like (setq org-bable-R-command "/full/path/to/R --slave --no-save") in your .emacs, although the exact format for Windows is going to be different. This is meant as a test, not as a fix: if that works, then you can figure out how to change your path and get rid of the hack. > > I tried evaluating (require 'ob-perl) and this yielded > > ob-perl > > in the minibuffer, and thereafter the perl code block executed properly. > Ok, that's promising. > I wonder if I need to put the path to R in my PATH variable? (come to > think of it, don't know why it's not already there); its absence has so > far not prevented me from using R via ESS. > Probably. Nick