Re: org-babel-R and windows ?

From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-babel-R  and windows ?
Date: Thu, 14 Jan 2010 09:37:32 +0100	[thread overview]
Message-ID: <87hbqpkroz.fsf@mundaneum.com> (raw)
In-Reply-To: 874ompiyk2.fsf@stats.ox.ac.uk

Hi Dan,

Dan Davison wrote:
> "d.tchin" <d.tchin-7V4A5QgKqXk@public.gmane.org> writes:
>> Dan Davison <davison <at> stats.ox.ac.uk> writes:
>>> The org-babel default is to invoke R as an external shell command, and I
>>> think this is what is causing the problem. It requires that the emacs
>>> function shell-command can use the string "R" to invoke an R process, i.e.
>>> the R installation and the shell path must be such that this is the case.
>>
>> Thank you for the information and explanation. It seems that the problem
>> comes from the windows shell.
>>
>> I try the following :  I explicitely told emacs to use bash
>> with the following instructions :
>> (setq explicit-shell-file-name "C:/msys/1.0/bin/bash.exe")
>> (setq shell-file-name explicit-shell-file-name)
>>
>> It works with bash.
>
> Thanks for that, I've stored your solution in the org-babel development repo
> with a view to modifying our code so that these probloems are minimised in
> the future, and we'll also make sure the documentation addresses this.

I'm a Windows user *and* an Ubuntu user for years, now, with one single common
`.emacs' file for both OS.

Therefore, I'll show you what I have in my `.emacs':

--8<---------------cut here---------------start------------->8---
;;*** ----[ 41.1 Single Shell

;; for single shell commands
(setq shell-file-name "bash")  ;; must be in the `PATH' (Windows users)

;;*** ----[ 41.2 Interactive Shell

;; for the interactive (sub)shell
(setq explicit-shell-file-name shell-file-name)
--8<---------------cut here---------------end--------------->8---

Almost the same, except the order (not important) and the fact that bash is
written in its simplest form: no hard-coded path, and no `.exe' suffix, so
that it works for both Win32 and Linux.

The only thing to do, for Windows users, is ensure that `bash.exe' (generally
located in `C:\cygwin\bin') is in the Windows PATH environment variable.

I would advice keeping such a construct, instead of full paths.

Best regards,
  Seb

-- 
Sébastien Vauban

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode