From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Vikas Rawal <vikaslists@agrarianresearch.org>
Cc: William Denton <wtd@pobox.com>,
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 10:58:37 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1605290943360.619@charles-berrys-macbook.local> (raw)
In-Reply-To: <5F862231-C04A-4BF6-8A2A-2377AF000374@agrarianresearch.org>
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-wait-for-file("type2"
[rest deleted]
`sit-for' is in this loop:
`(while (not (file-exists-p file)) (sit-for (or period 0.25)))'
which suggests that the file to which the results should be written is not
being created or there is an issue with `sit-for'.
Does anyone know why `sit-for' is used here rather than `sleep-for'?
I ask because I see that `sit-for' because it seems to me that `sleep-for'
would be enough and `sit-for' has inline comments that suggest some
unresolved issues.
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?
Chuck
next prev parent reply other threads:[~2016-05-29 17:58 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 [this message]
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.OSX.2.20.1605290943360.619@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=vikaslists@agrarianresearch.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).