[ESS-bugs] ess-mode 15.09-devel [git: f0c5d8019ead3d8b206ca85f039f6a4841e8ac08]; .ess commands are visible in remote buffers

[Vitalie Spinu]

 >>> Sam Steingold on Wed, 06 May 2015 18:12:42 -0400 wrote:

 >> * Vitalie Spinu <fcvahivg at tznvy.pbz> [2015-05-06 22:58:42 +0200]:
 >> 
 >> I am always on remotes but through tramp and everything works fine.

 > tramp/ssh is unacceptable - R dies on lost connection (with all the
 > unfinished computations).

Yes. I know. I am suffering from the same pain.

 >> ESS commands exit prematurely with xterm.

 > I am afraid I do not understand what you mean.
 > Sorry.

When we send commands we wait for prompt (just like TRAMP) does. It
seems that those funny characters often contain ">" at the end of output
which we interpret as prompt and exit from the waiting loop. If we exit
prematurely, the output of of our commands ends in user buffer.

 >> It's probably because of the control characters from xterm which
 >> terminate with >. I cannot think of any other reason.

 > this seems to imply that I should disabuse R of he illusion that it
 > is running under xterm. do you know what tramp sets TERM to?

Yes. Something of that kind. But honestly, I have no idea what's really
going on. I need to try your code and learn how exactly term.el works to
really see what's going on.

I am think that if you replace make-term with make-comint it might work
as expected.

A year or so ago I promised to you to setup an infrastructure for
automatic screen connections. Never got down to it, but might do now. I
am getting more and more pissed off with tramp ways these days.

 Vitalie