[ESS-bugs] ess-mode 13.05 [<unknown>]; ess-remote with eshell/ssh error

[Vitalie Spinu]

Indeed, I have just checked it, ess-remote breaks during the source
injection. I don't know why as yet.

TRAMP is indeed a better way to go about it. Put something like 
   
   Host amazon
      Hostname ec2-174-129-60-172.compute-1.amazonaws.com
      User ubuntu
      IdentityFile ~/.ssh/amazon.pem
   
in your .ssh/config

then C-x C-f /ssh:amazon: RET. Then M-x R. There might be an even more
direct way.

Keeping ess-remote alive is not a big deal and for most users ess-remote
is the simplest way to go about it. So I think we should think twice
before removing it.

I also never used x2go, but from what I can see it is a remote desktop
solution. Rodney please correct me if I am wrong, the user will have to
run Emacs (and X) on a remote server. And that is not what is often
needed or even possible.

    Vitalie

 >> "Sebastian P. Luque" <spluque at gmail.com>
 >> on Tue, 21 May 2013 08:18:33 -0500 wrote:

 > On Tue, 21 May 2013 08:02:21 -0400,
 > Sam Steingold <sds at gnu.org> wrote:

 >> On Mon, May 20, 2013 at 5:57 PM, Rodney Sparapani <rsparapa at mcw.edu> wrote:
 >>> I think ess-remote's days are numbered.  We haven't gotten around to
 >>> actually removing it.  But, it is from a paradigm that is now
 >>> antiquated with faster pipes and newer technology like NX/x2go/etc.

 >> Fine. How do I run R on a remote machine?  Thanks!

 > I haven't yet used the options that Rodney mentions, but one that works
 > well enough for me relies on TRAMP.  Simply start R while working with
 > your script remotely as you normally would with TRAMP, making sure the
 > process is associated with your remote script.  R will be running on
 > that machine.  If you're using SSH, it's important to have pager="cat"
 > for the help system to work properly, so I use this in ~/.Rprofile:

 >     if (Sys.getenv("SSH_CONNECTION") != "") options(pager="cat")