[ESS] eldoc doesn't work in remote sessions
andreas.leha at med.uni-goettingen.de
Wed Sep 18 20:46:29 CEST 2013
see inline below.
Kasper Daniel Hansen <kasperdanielhansen at gmail.com> writes:
> The immense advantage of screen is that it has been available on every HPC
> cluster I have ever had access to. Alternatives (mosh as an alternative to
> ssh for example) almost invariable requires buy-in from system
> administrators who may be entirely uninterested in helping you: in other
> words, a good solution using screen would be great and I am excited to see
> Li working on this. I would love love love to be able to set up a single
> command for doing all of this in one go (including connecting to a running
> screen session, if present and also be able to use something like qrsh to
> get onto a cluster node), but have not had the time to dedicate to this.
I agree with all of that.
I gather, that the proposed 'solution' is to start a remote emacs inside
the screen. But that has drawbacks, if I work on several remote hosts
So, I would also love to see that workflow conveniently supported by ess.
> On Wed, Sep 18, 2013 at 11:35 AM, Rodney Sparapani <rsparapa at mcw.edu> wrote:
>> On 09/18/2013 12:54 AM, Li Bowen wrote:
>> > Thank you both for reply.
>> > The reason to use ssh.el is because I want to run R in a*screen*
>> > to avoid loss of work due to connection loss and also be able to
>> > continue working on different clients. I know tramp is much easier.
>> Hi Li:
>> Well, screen is one way to combat connection loss. FYI: I have moved on to
>> nxclient and it's free, open source descendent x2go.
>> Rodney Sparapani, PhD
>> Manager of Statistical & Computational Operations
>> Center for Patient Care and Outcomes Research (PCOR)
>> Medical College of Wisconsin (MCW), Milwaukee, USA
>> ESS-help at r-project.org mailing list
> [[alternative HTML version deleted]]
> ESS-help at r-project.org mailing list
More information about the ESS-help