[ESS] Running sas remotely

Rodney Sparapani rsparapa at mcw.edu
Thu Oct 6 16:36:53 CEST 2005


Cameron Hooper wrote:

>Hi
>
>  
>
>>Open up a telnet or equivalent window on the remote machine and run
>>a remote emacs in that window.   Then work as you have been working.
>>    
>>
>
>I did not express myself clearly. At the moment I do exactly as you 
>suggest, I think. Open up a terminal window, ssh to the remote machine 
>and then run emacs. This is works fine. But ...
>
>It would be nice to work inside a windowing (GUI) version of emacs. I 
>can achieve this by using X-Windows, but to be honest I don't like this 
>option. X-windows can be slow, and the available fonts are, IMHO, 
>difficult to read. But I have a lovely version of emacs that runs on my 
>Mac. I can use this emacs on my local machine to open a SAS file stored 
>on the remote machine via TRAMP. The question is, can I then actually 
>submit regions of this SAS file to the SAS engine on the remote 
>machine. In other words, I want to run emacs locally and submit SAS 
>code remotely.
>
>Cameron
>  
>
Hi Cameron:

This should work automatically.  That's how I've done alot of work from
home.  I've not had much success with tramp, but I haven't tried recently. 
I'll take another look at it.  Did you check the manual?  Hmm, checking 
now .... 
Does this help?

10.4 ESS(SAS)-Batch SAS processes
=================================

Submission of a SAS batch job is dependent on your environment.
`ess-sas-submit-method' is determined by your operating system and your
shell.  It defaults to `'sh' unless you are running Windows or Mac
Classic.  Under Windows, it will default to `'sh' if you are using a
UNIX-imitating shell; otherwise `'ms-dos' for an MS-DOS shell.  On Mac
OS X, it will default to `'sh', but under Mac Classic, it defaults to
`'apple-script'.  You will also set this to `'sh' if the SAS batch job
needs to run on a remote machine rather than your local machine.  This
works transparently if you are editing the remote file via ange-ftp/EFS
or tramp.  Note that `ess-sas-shell-buffer-remote-init' is a Local
Variable that defaults to `"ssh"' which will be used to open the buffer
on the remote host and it is assumed that no password is necessary,
i.e. you are using `ssh-agent'/`ssh-add' or the equivalent (see the
discussion about Local Variables below if you need to change the
default).

   However, if you are editing the file locally and transferring it
back and forth with Kermit, you need some additional steps.  First,
start Kermit locally before remotely logging in.  Open a local copy of
the file with the `ess-kermit-prefix' character prepended (the default
is `"#"').  Execute the command `M-x ess-kermit-get' which
automatically brings the contents of the remote file into your local
copy.  If you transfer files with Kermit manually in a `*shell*'
buffer, then note that the Kermit escape sequence is `C-q C- c' rather
than `C- c' which it would be in an ordinary terminal application, i.e.
not in an emacs buffer.  Lastly, note that the remote Kermit command is
specified by `ess-kermit-command'.




More information about the ESS-help mailing list