From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: William Denton <wtd@pobox.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Trouble evaluating R source code blocks with C-c C-c
Date: Sun, 29 May 2016 07:32:24 +0530 [thread overview]
Message-ID: <9F364365-564B-47E0-8551-B56977278001@agrarianresearch.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1605281025120.13862@shell.miskatonic.org>
> On 28-May-2016, at 7:57 pm, William Denton <wtd@pobox.com> 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 system are struggling to keep up. But I could be wrong.
>
> I've had the same kind of thing happen---but C-g (sometimes many) to kill the command, then rerunning, usually works without any trouble. Some strange combination of CPU and RAM and all that, the kind of thing that's not easily reproducible.
>
This seems to be write. Upgrading ess did not help.
The odd thing is that running the same code by doing C-‘ to open a temporary R buffer and running to code from there works fine. But then I come back to the org buffer, C-c C-c, and the whole thing just freezes. The R session shows that the code is running. I have to use C-g in the org-buffer, which releases the org buffer, and C-c several times in the R session, to stop the commands. If I have waited enough, doing C-c C-c at the end in the R session ends the command and actually shows the output of the last command in R buffer. Which means that the last command had been completed. But the output was not inserted in the org buffer, and R was going on doing something.
Let me try ‘debug-on-quit'
Vikas
prev parent reply other threads:[~2016-05-29 2:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 14:33 Trouble evaluating R source code blocks with C-c C-c Vikas Rawal
2016-05-26 18:52 ` John Hendy
2016-05-28 7:58 ` Vikas Rawal
2016-05-28 14:27 ` William Denton
2016-05-28 16:57 ` Charles C. Berry
2016-05-28 17:01 ` Charles C. Berry
2016-05-29 12:31 ` Vikas Rawal
2016-05-29 13:13 ` Vikas Rawal
2016-05-29 17:58 ` Charles C. Berry
2016-05-30 0:37 ` Vikas Rawal
2016-05-30 1:18 ` Charles C. Berry
2016-05-30 10:24 ` Vikas Rawal
2016-05-30 16:22 ` Charles C. Berry
2016-05-29 2:02 ` Vikas Rawal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9F364365-564B-47E0-8551-B56977278001@agrarianresearch.org \
--to=vikaslists@agrarianresearch.org \
--cc=emacs-orgmode@gnu.org \
--cc=wtd@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).