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

[Sam Steingold]

FWIW, I don't see how nx/x2go can be _replacing_ ess-remote.
I need to be running local emacs/ESS talking to remote R.
any solution which involves running a remote Emacs is not acceptable to
me because of network speed and reliability issues.


> * Rodney Sparapani <efcnencn at zpj.rqh> [2013-05-21 09:33:09 -0500]:
>
> On 05/21/2013 09:15 AM, Vitalie Spinu wrote:
>> 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
>
> That is correct.  You run emacs on the server where R resides.  However,
> the definition of desktop varies, i.e. you can specify that there is no
> desktop: just your emacs window for performance reasons.  You have to
> try it before dissing it ;o)  It really screams.  But, tramp is OK too;
> I just forgot about it.
>
> However, I will say that debugging these ess-remote issues is a
> complete nightmare with pseudo-terminals/pipes/etc.  If you don't
> believe me, then fix ESS[SAS] to work remotely!  I would suggest that
> we prioritize our bug-fixing elsewhere.  I, personally, am not going
> to try to fix ess-remote in any way.  Technology has moved on and
> we should utilize it to simplify ESS rather than complicate it.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 13.04 (raring) X 11.0.11303000
http://www.childpsy.net/ http://honestreporting.com
http://iris.org.il http://americancensorship.org http://think-israel.org
A bullet affects the way the brain functions even when it hits the butt.