Tom,
what happens with:
(Emacs)
M-x ssh
t
(you should have the remote shell buffer now)
R
(once R is started)
M-x ess-remote
r
?
Claudia
--
Claudia Beleites
Spectroscopy/Imaging
Institute of Photonic Technology
Albert-Einstein-Str. 9
07745 Jena
Germany
email: claudia.belei...@ipht-jena.de
p...@potis.org writes:
> When I move R and Rscript out of my path, as expected, I also
> have problems. If I use tramp to connect to remote, open a shell
> there with M-x eshell, and type 'env' , my path is the path on
> local.
This is the correct behaviour of eshell:
/scp:slbps0:/root $ which
-Tom Roche Thu, 12 Jan 2012 11:56:25 -0500>>>
> - Starting R from the resulting tramp buffer fails with either of two
> messages in buffer=*Messages*
...
> > Cannot read history file /scpc:t:/home/me/.Rhistory
This is normal. Not a problem.
> I'm
> also guessing I might have a configuration probl
Tom Roche Thu, 12 Jan 2012 11:56:25 -0500
>>> * I have access to the cluster [where I want to run R] configured
>>> [in my linux laptop's .ssh/config] such that I can `ssh t` from
>>> commandline.
Note also that I'm using keychain
http://www.cyberciti.biz/faq/ssh-passwordless-login-with-keyc
Tom Roche Thu, 12 Jan 2012 11:56:25 -0500
>>> * I have access to the cluster [where I want to run R] configured
>>> [in .ssh/config] such that I can `ssh t` from commandline.
>>> 1 I can open an R file on the cluster with
>>> `C-x C-f /t:/home/me/onlyOrigDN2.r`
>>> from my laptop, and note
5 matches
Mail list logo