Hi all,
Thomas Alexander Gerds t...@biostat.ku.dk writes:
Hi Bastien
I think that I can describe the problem a bit better now. It is not
related to the silent option but occurs whenever :results value.
Emacs freezes due to the following line in
hmm. I agree that this should be handled by ESS and I have not given up yet.
as indicated in my previous mail, I dont know how to test if an
R-session is remote because the command ess-remote deletes all local
variables. a hack would be to let the R-process evaluate
yes, I am using ESS. ess-remote allows me to evaluate R-code from the local
emacs-session on a remote machine connected to via ssh.
there are two problems:
1) the remote machine cannot write to org-babel-temp-file because the
tmp-directory exists on the local machine. here we could add
It is a shame that this can't be handled gracefully either through ESS
or R code.
I agree it would be nice to raise a warning rather than hang waiting for
a file which won't ever exist. So, how can we tell from the Babel
source if the R session is remote?
Thanks,
Thomas Alexander Gerds
Bastien b...@gnu.org writes:
Hi Thomas,
thanks for the follow-up.
Thomas Alexander Gerds t...@biostat.ku.dk writes:
I think that I can describe the problem a bit better now. It is not
related to the silent option but occurs whenever :results value.
Emacs freezes due to the following
Hi Thomas,
thanks for the follow-up.
Thomas Alexander Gerds t...@biostat.ku.dk writes:
I think that I can describe the problem a bit better now. It is not
related to the silent option but occurs whenever :results value.
Emacs freezes due to the following line in
Hi Bastien
I think that I can describe the problem a bit better now. It is not
related to the silent option but occurs whenever :results value.
Emacs freezes due to the following line in
org-babel-comint-eval-invisibly-and-wait-for-file
(while (not (file-exists-p file)) (sit-for (or period
Hi Thomas,
Thomas Alexander Gerds t...@biostat.ku.dk writes:
Using the silent option together with a remote R session block (started
via ssh.el and ess-remote), like this:
#+BEGIN_SRC R :results silent :exports results :session *ssh gauss* :cache
yes
a=1
1
#+END_SRC
produces:
Bastien writes:
#+BEGIN_SRC R :results silent :exports results :session *ssh gauss* :cache
yes
[…]
with `:results output' instead of `:results: silent' everything works
fine.
Please let us know if the documentation* needs some clarification here,
or if this is a bug -- maybe someone
Using the silent option together with a remote R session block (started
via ssh.el and ess-remote), like this:
#+BEGIN_SRC R :results silent :exports results :session *ssh gauss* :cache
yes
a=1
1
#+END_SRC
produces:
,
|[1] 1
| Warning message:
| In file.rename(tfile,
Thomas Alexander Gerds t...@biostat.ku.dk writes:
Using the silent option together with a remote R session block (started
via ssh.el and ess-remote), like this:
#+BEGIN_SRC R :results silent :exports results :session *ssh gauss* :cache
yes
a=1
1
#+END_SRC
produces:
,
|[1]
yes, I am quite sure. here is the org code
,
|
| #+BEGIN_SRC R :results silent :exports results :session *ssh gauss* :cache
yes
| a=1
| 1
| #+END_SRC
|
| #+BEGIN_SRC R :results output :exports results :session *ssh gauss* :cache
yes
| a=1
| 1
| #+END_SRC
|
| #+RESULTS[2013-03-13
12 matches
Mail list logo
