mailing-list for TeXmacs Users

[Joris van der Hoeven <address@hidden>]

Dear Michael,

On Wed, Nov 18, 2009 at 01:09:49AM +0100, Michael Lachmann wrote:
> I see.. so you are saying that one should figure the exact flags/ 
> configurations one needs to have ssh allocate a pseudo-terminal when you 
> call something like
> ssh host /usr/bin/R
> instead of doing
> ssh host
> which launches a shell, in which you have to then run R.
>
> And then, if you want a series of remote hosts, you need to do
> ssh host1 ssh host2 R
> again with some flags, if possible.
>
> Wow! It works! And I spent all day on the train getting tm_r to work  
> "well" without allocating a pseudoterminal. At least I cleaned up the  
> code a bit in the process...
>
> The flags for ssh are -t -t
>
> So, to log in remotely, you have to use
>
> ssh -t -t host -l user path_to_R
>
> or
> ssh -t -t host1 -l user1 ssh -t -t host2 -l user2 path_to_R
> (which is what I just tried, and it worked!)
>
> And you think the best is to require the user to set up everything so  
> that no username/password is needed to log to the hosts, and the command 
> is always R, or should the user just set things up so that no password is 
> needed, but she can still specify host/username combinations and command 
> to run?

Thanks for reminding the procedure to me.
I have been thinking about a way to automate remote sessions.
Unfortunately, this is not going to be really simple.
First of all, detection of plug-ins will not work as implemented now,
so the user will have to manually enter the remote host and
the versions of the installed software. Initialization scripts
also have to be transferred to the remote host first.
Finally, some minor changes may be necessary for
the communication itself.

Although I do agree that it would be a nice feature
if we could run all plug-ins remotedly,
it will take at least several days or a week for me
to implement this. I do not have time for that now.

Best wishes, --Joris