starting inferior Splus process iESS[S]

[Steve McKinney]

Thank you very much Rich.

I have Emacs/ESS/S-PLUS up and running now.

I had added paths to s-plus and cygwin folders
to my Windows PATH variable, but had
not rebooted my machine so these
folders were not in the path that
subsequent shell processes were getting.

c:\ProgramFiles\Insightful\Splus61\cmd;c:\cygwin\bin


After rebooting my machine, everything
works swimmingly well.

I really appreciate your patience and suggestions.

It was your 

M-x load-file correctpath/ess/lisp/msdos.el
M-x msdos
M-x shell

hint that allowed me to see the bad path variable
in a shell window running in emacs.


Thanks again,


Best

Steven McKinney
Consulting Services
Insightful Corporation
 
smckinney at insightful.com
 
tel: (800) 569-0123 x349
tel: (206) 283-8802 x349
fax: (206) 283-8691
 
Insightful Corporation
1700 Westlake Avenue North, Suite 500
Seattle, Washington 98109-3044 USA


Insightful Corporation (www.insightful.com) 
provides analytical solutions leveraging 
S-PLUS, StatServer, S-PLUS Analytic Server, 
Insightful Miner, and consulting services.



> -----Original Message-----
> From: Rich Heiberger [mailto:rmh at surfer.sbm.temple.edu]
> Sent: Wednesday, April 16, 2003 2:43 PM
> To: ess-help at stat.math.ethz.ch; Rich Heiberger; Steve McKinney
> Subject: RE: starting inferior Splus process iESS[S]
> 
> 
> ESS and emacs can handle any length filename.  They only have problems
> with embedded blanks.
> 
> On the code 128,
> a. Does the command
> c:/programfiles/insightful/splus61/cmd/splus.exe 
> /MULTIPLEINSTANCES S_PRINT_COMMAND=gnuclientw.exe S_PROJ=e:/foo
> work when manually typed into the *shell* buffer running cygwin sh?
> 
> Does the corresponding command
> c:\programfiles\insightful\splus61\cmd\splus.exe 
> \MULTIPLEINSTANCES S_PRINT_COMMAND=gnuclientw.exe S_PROJ=e:\foo
> work when manually typed into the *shell* buffer running msdos?
> (which you can get with
> M-x load-file correctpath/ess/lisp/msdos.el
> M-x msdos
> M-x shell
> )
> Doe it work when typed into the msdos prompt window?
> 
> b. if typing into the msdos prompt window causes trouble, 
> then run down the
> hall and ask one of the systems people to look at your computer.
> 
> c. Since you are at Insightful, running down the hall for a 
> systems person
> might still work for the other situations.  Many of the Unix users at
> Insightful also use ESS, and some of the Windows people do as well.
> 
> On gnuserv/gnuclient:
> You will notice (once you get it running) that by default ESS sets the
> .S-Plus options editor, pager, help.pager to gnuclient gnuclientw and
> gnuclientw.
> 
> When I want to look at an S-Plus function (lm.default, for example),
> I type at the command line
> 
> page(lm, file="lm.s")
> 
> and the file is displayed in an emacs buffer where I have 
> full editing control.
> If I forget to give it a file name, it places it in an emacs 
> buffer with
> a temporary randomly generated name.
> 
> The help files that use the windows help system continue to 
> use the windows
> help system.  the ones that use the older style (mostly non-Insightful
> libraries now) place their help files in appropriate emacs buffers.
>