On Mon, 30 May 2016, Vikas Rawal wrote:
Thanks.
The code still seems to freeze.
The backtrace now is.
OK, let me abbreviate this by cutting off the ends of long lines:
Debugger entered--Lisp error: (quit)
process-send-string(# ".ess.eval(\"lm(log_cal~sector+ [...]
ess-send-string--fallb
Thanks.
The code still seems to freeze.
The backtrace now is.
Debugger entered--Lisp error: (quit)
process-send-string(#
".ess.eval(\"lm(log_cal~sector+sex+AgeChild+AgeAdult+foodprice+log(MPCE)+state_region,data=regdata,weights=weight)->reg\nlm(adj_cal~sector+sex+AgeChild+AgeAdult+foodprice+l
On Sun, 29 May 2016, Vikas Rawal wrote:
Vikas, can you edit the `sit-for' to `sleep-for' in
`org-babel-comint-eval-invisibly-and-wait-for-file'
and `eval-defun' the result and see if that has any effect?
Sorry, given my limited ability with lisp, I do not really
understand. Could you
>
> Vikas, can you edit the `sit-for' to `sleep-for' in
>
> `org-babel-comint-eval-invisibly-and-wait-for-file'
>
> and `eval-defun' the result and see if that has any effect?
>
Sorry, given my limited ability with lisp, I do not really understand. Could
you please spell out what do I have t
On Sun, 29 May 2016, Vikas Rawal wrote:
And this time it has this additional line:
run-hook-with-args-until-success(org-babel-execute-safely-maybe)
Actually, I saw that line in your previous posting.
But this may help:
--
sit-for(0.25)
org-babel-comint-eval-invisibly-
And this time it has this additional line:
run-hook-with-args-until-success(org-babel-execute-safely-maybe)
--
sit-for(0.25)
org-babel-comint-eval-invisibly-and-wait-for-file("type2"
"/var/folders/hj/hqfjch716qg5php160jbtfghgn/T/babel-53134TSq/R-53134vJF"
"{\nfunc
Does this back-trace say anything?
sit-for(0.25)
org-babel-comint-eval-invisibly-and-wait-for-file("type2"
"/var/folders/hj/hqfjch716qg5php160jbtfghgn/T/babel-53134TSq/R-53134IWW"
"{\nfunction(object,transfer.file) {\nobject\ninvisible(\n
if (\n
> On 28-May-2016, at 7:57 pm, William Denton wrote:
>
> On 28 May 2016, Vikas Rawal wrote:
>
>> Thanks John. Appreciate that you cared to respond to such a vague query. I
>> am at a loss with this one. It does not happen all the time. I think it
>> happens when I am processing large datasets,
p.s. one more thing - below
On Sat, 28 May 2016, Charles C. Berry wrote:
On Sat, 28 May 2016, William Denton wrote:
On 28 May 2016, Vikas Rawal wrote:
Thanks John. Appreciate that you cared to respond to such a vague query. I
am at a loss with this one. It does not happen all the time. I t
On Sat, 28 May 2016, William Denton wrote:
On 28 May 2016, Vikas Rawal wrote:
Thanks John. Appreciate that you cared to respond to such a vague query. I
am at a loss with this one. It does not happen all the time. I think it
happens when I am processing large datasets, and CPUs and RAM of my
On 28 May 2016, Vikas Rawal wrote:
Thanks John. Appreciate that you cared to respond to such a vague query. I am
at a loss with this one. It does not happen all the time. I think it happens
when I am processing large datasets, and CPUs and RAM of my system are
struggling to keep up. But I coul
Thanks John. Appreciate that you cared to respond to such a vague query. I am
at a loss with this one. It does not happen all the time. I think it happens
when I am processing large datasets, and CPUs and RAM of my system are
struggling to keep up. But I could be wrong.
Let me take your advice
Could you give a minimal example? The behavior does ring a bell, but I
can't recall what the solution might have been. I'd be happy to try
and reproduce if you'd like.
I think my typical go-to is to wipe ESS and re-download/make... That's
all I'm good for without more info.
Sorry!
John
On Thu,
I face a strange problem with evaluating R source code blocks. Occasionally,
they take much longer to produce the results when I try to evaluate them with
C-c C-c. On the other hand, if I do C-c ‘, go to a temporary R buffer, and
evaluate the code, everything works fine. In face, when I use C-c
14 matches
Mail list logo