From: William Denton <wtd@pobox.com>
To: Vikas Rawal <vikaslists@agrarianresearch.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Trouble evaluating R source code blocks with C-c C-c
Date: Sat, 28 May 2016 10:27:59 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1605281025120.13862@shell.miskatonic.org> (raw)
In-Reply-To: <2E8B017B-F4AB-454D-81A1-E61F55F4F958@agrarianresearch.org>
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.
Relatedly, sometimes if I have ":results output" for one block and then
":results values" for the next one, the second block picks up the output from
the first one. But then other times not! Seems to depend on how intensive the
R work is.
Bill
--
William Denton :: Toronto, Canada :: https://www.miskatonic.org/
Caveat lector.
next prev parent reply other threads:[~2016-05-28 14:28 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 [this message]
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
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=alpine.DEB.2.02.1605281025120.13862@shell.miskatonic.org \
--to=wtd@pobox.com \
--cc=emacs-orgmode@gnu.org \
--cc=vikaslists@agrarianresearch.org \
/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).