Posted
over 8 years
ago
by
Andreas Leha
Hi Sam,
Sam Steingold <sds< at >gnu.org> writes:
Thanks. Yes, I have seen your set-up. I have meant to give that a try
for quite some time. It is still on my list.
Regards,
Andreas
______________________________________________
ESS-help< at >r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
|
Posted
over 8 years
ago
by
Sam Steingold
Both tmux and screen are far too "screen-oriented".
My solution using dtach has been working perfectly for me for over a
year:
http://stackoverflow.com/a/22703777/850781
--8<---------------cut here---------------start------------->8---
... [More]
(defvar R-remote-host "remote-server")
(defvar R-remote-session "R")
(defvar R-remote-directory "~")
(defun R-remote (&optional remote-host session directory)
"Connect to the remote-host's dtach session running R."
(interactive (list
(read-from-minibuffer "R remote host: " R-remote-host)
(read-from-minibuffer "R remote session: " R-remote-session)
(read-from-minibuffer "R remote directory: " R-remote-directory)))
(pop-to-buffer (make-comint (concat "remote-" session)
"ssh" nil "-t" "-t" remote-host
"cd" directory ";"
"dtach" "-A" (concat ".dtach-" session)
"-z" "-E" "-r" "none"
inferior-R-program-name "--no-readline"
inferior-R-args))
(ess-remote (process-name (get-buffer-process (current-buffer))) "R")
(setq comint-process-echoes t))
--8<---------------cut here---------------end--------------->8---
[Less]
|
Posted
over 8 years
ago
by
Andreas Leha
Hi,
[ ... ]
I just want to report that these problems seem to not occur when I use
`multi-term' as the terminal mode in emacs. There, I seem to see 'Wuff
|
Posted
over 8 years
ago
by
Vincent Goulet
Thanks to ever improving scripts, my distributions are up-to-date.
Windows: http://vgoulet.act.ulaval.ca/en/emacs/windows/
OS X: http://vgoulet.act.ulaval.ca/en/emacs/mac/
v.
______________________________________________
ESS-help< at >r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
|
Posted
over 8 years
ago
by
Martin Maechler
We have just released ESS 15.09-2.
After release of 15.09 on Sept.24
and a first patch release 15.09-1 on Oct.26,
this is another patch release for 15.09.
It fixes small glitches with (the new more flexible and
powerful) indentation engine.
In
... [More]
addition
- it improves Roxygen editing (line wrapping; filling);
- knitr/Sweave interface cosmetics, notably a new
M-x ess-swv-weave-PDF (bound to M-n v ('v' for 'v'iew)).
- SAS and coda/BUGS improvements
- prevents infinite loops in some border cases
All in all only small changes, but really a reason for a
Christmas gift release of ESS - one day after
the R 3.2.3 "Wooden Christmas-Tree" release.
DOWNLOAD:
The latest released version of ESS as always available from
ESS web page (http://ess.r-project.org) e.g. directly as
http://ess.r-project.org/downloads/ess/ess-15.09-2.zip
---
In the name of the ESS Core team,
Martin Maechler
______________________________________________
ESS-help< at >r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
[Less]
|
Posted
over 8 years
ago
by
Andreas Leha
Hi Vitalie,
Vitalie Spinu <spinuvit< at >gmail.com> writes:
Thanks for following that up even when travelling.
Well, this was more meant as a comment to your suggestion to ask for R
to change the prompt. I was testing this running R
... [More]
outside of emacs and
there is this difference. So, I guess that is what the reply from R's side
would be: There is a different prompt already.
As to your suggestion of setting `ess-eval-visibly' to t and using the
trailing '+' as an indicator: I think the speed loss is too much to
trade in for the better GUI experience. I have set `ess-eval-visibly' to
nil as well.
Ideally, I think it would be the much better experience if the spinning
wheel would
- appear only if R was busy and was not waiting for more user input
- appear directly in the R buffer instead of the mode line
I understand that this is not straight forward to achieve. But
Christmas is close and so wishlists mights be written...
Regards,
Andreas
______________________________________________
ESS-help< at >r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
[Less]
|
Posted
over 8 years
ago
by
Vitalie Spinu
Sorry for late reply (I am travelling).
You are probably having the default `ess-eval-visibly` set to t. I think most of
people switch to `nil` eventually because the default is very slow as it sends
the code line by line.
Indeed, when
... [More]
`ess-eval-visibly` is t, we probably can reliably track the prompt.
But then I don't understand your original problem. If you see trailing + that
means your code is incomplete, otherwise the program is busy.
Vitalie
______________________________________________
ESS-help< at >r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
[Less]
|
Posted
over 8 years
ago
by
Christopher Paisey
I find that after upgrading my mac to El Capitan, I am unable to run
commands to import files such as
"assD<-read.csv(file.choose())" and it will just get stuck on the loading
page until I force quit R. I have tried reinstalling R 3.2.2 but this
... [More]
didn't help.
Thank you for your time,
Chris
[[alternative HTML version deleted]]
______________________________________________
ESS-help< at >r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
[Less]
|
Posted
over 8 years
ago
by
Andreas Leha
Hi Vitalie
Vitalie Spinu <spinuvit< at >gmail.com> writes:
I cannot reproduce this. I do get an empty line (while waiting) in the
former case, while I get a '+' prompt in the second case. I seem to
still miss the point:
,----
| >
... [More]
## complete:
| > {
| + Sys.sleep(10)
| + }
|
`----
vs
,----
| > ## incomplete:
| > {
| + Sys.sleep(10
| +
`----
Regards,
Andreas
______________________________________________
ESS-help< at >r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
[Less]
|
Posted
over 8 years
ago
by
Vitalie Spinu
That's what we are tracking right now - difference between + and >. That's not
enough for what you need.
Both of the following produce same result
## complete:
{
Sys.sleep(10)
}
## incomplete:
{
Sys.sleep(10
The current tracking
... [More]
is not even enough for what it was intended for. For
example evaluating the following paragraph will not show as busy:
Sys.sleep(.1)
Sys.sleep(100)
And that's the most annoying side of the current system. I see only one way for
a partial fix - sending a NOOP before every eldoc or completion command to check
for actual status of the sub-process. Not sure how reliably it will work though.
Vitalie
______________________________________________
ESS-help< at >r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
[Less]
|