[ESS] rterm path

Dale Steele dale.w.steele at gmail.com
Wed May 19 14:24:42 CEST 2010

I used subversion to obtain the most recent version (revision 4327),
and started emacs on my 64 bit Windows machine with the following in
my .emacs file:

(load "~/ess-svn/lisp/ess-site.el")

Emacs responds with ....
Warning (initialization): An error occurred while loading

Wrong type argument: stringp, nil

Ideas about what I am doing wrong?

Thanks. --Dale

Error backtrace below....

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  (setq ess-r-versions-created (ess-r-versions-create))
  (let ((ess-s-versions-created) (R-newest-list ...)) (if
ess-microsoft-p (progn ... ... ...) (setq ess-s-versions-created ...))
(setq ess-r-versions-created (ess-r-versions-create)) (setq
ess-versions-created (ess-flatten-list ...)) (when
ess-versions-created (let ... ...)))
  eval-buffer(#<buffer  *load*<2>> nil
"c:/Users/dsteele/ess-svn/lisp/ess-site.el" nil t)  ; Reading at
buffer position 22182
"c:/Users/dsteele/ess-svn/lisp/ess-site.el" nil nil)
  eval-buffer(#<buffer  *load*> nil "c:/Users/dsteele/.emacs" nil t)
; Reading at buffer position 36
"c:/Users/dsteele/.emacs" t t)
  load("~/.emacs" t t)
  #[nil "\205\264

On Fri, Apr 23, 2010 at 2:49 PM, RICHARD M. HEIBERGER <rmh at temple.edu> wrote:
> Here is the outline of the ESS fix for finding the 64 bit R on Windows.
> I would like some e-lisp help now, and then when I get access to a 64 bit
> machine, I can finish it.
> The problem is that Windows (I assume it is Windows, and not R-core) places
> the 32- and 64-bit R in
> non-parallel places
> C:\\Program Files\\R\\R-2.11.0-x64\\bin\\Rterm
> C:\Program Files (x86)\R\R-2.11.0\bin\Rterm.exe
> and the ess-find-rterm function in essd-r.el assumes they will be in
> parallel.
> I believe the repair consists of modifying the function ess-find-rterm to
> allow the variable
> ess-R-root-dir to be a list containing more than one value.  I can do it
> awkwardly and slowly.
> I hope Stephen can help by doing it elegantly and quickly.
> Then the variable ess-program-files in ess-cust.el needs to be initialized
> to the list
> '((w32-short-file-name (getenv "ProgramFiles")) (w32-short-file-name (getenv
> "ProgramFilesx64")))
> The initialization and the function need to behave sensibly when either of
> the environment variables
> is empty.
> I don't have a 64 bit machine now, so I am guessing the name of the
> environment variable that I
> labeled ProgramFilesx64 here.  Dale, can you help by sending the variable
> name to 'Reply All'
> for this email (I took this off ESS-help and moved it to ess-core).
> Rich

More information about the ESS-help mailing list