From: John Hendy <jw.hendy@gmail.com>
To: nicholas.dokos@hp.com
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: R and babel on Windows problem
Date: Mon, 2 Jul 2012 17:16:20 -0500 [thread overview]
Message-ID: <CA+M2ft8udMiG3j6j9rZGBHBdTuxUCoGo6AjWOih+TNOWNqofAg@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft_UOax7-3=xzxd63DYeh+SzaJ0_1xbsD85HdX1ru4z-7Q@mail.gmail.com>
>
> Anyway:
> - Visited ob-R.el in emacs
> - Found org-babel-R-evaluate-external-process
> - Put the cursor on the line =(defun org-babel-R-evaluate-external-process=
> - Did =M-x C-M-x= and the minibuffer echoed the name of the function
> - Visited my file, test.org and did =C-c C-c= on the R babel block
> - Nothing different occurred; I just got "The system cannot find the
> path specified"
>
> I tried the above again with regular 'ol org-babel-R-evaluate just in
> case and had the same results.
>
> I'm clearly goofing something but have no idea what it is.
>
Okay. I think I may have triggered =edebug-all-defs= when I was
tinkering around earlier and from the page about "instrumenting"
edebug it seemed like that could tweak some things undesirably. I got
that fixed and turned on edebug for
org-babel-R-evaluate-external-process and am getting nothing. The
modeline in my test file has turned to "Org *Debugging* Fill" but
still produces none of the incremental evaluation pauses I would have
expected.
I tried the same with org-babel-execute-src-block in ob.el since
that's what's called first and am still getting no new activity from
edebug. Just the same message about the path.
John
>
> John
>
>
>>
>> If you mess it up (and you probably will a few times), no problem: just try
>> again. And be patient!
>>
>> Good luck,
>> Nick
>>
>>
>>
>>>
>>> John
>>>
>>>
>>> >
>>> > Nick
>>> >
>>> >> Using =M-x R= works find. ESS is finding R. I successfully loaded a
>>> >> .csv, ggplot2 and plotted.
>>> >>
>>> >>
>>> >> John
>>> >>
>>> >> John
>>> >>
>>> >> >
>>> >> > Nick
>>> >> >
>>> >>
>>>
next prev parent reply other threads:[~2012-07-02 22:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 17:46 R and babel on Windows problem John Hendy
2012-06-29 14:59 ` Alexander Vorobiev
2012-06-29 15:24 ` John Hendy
2012-06-29 17:12 ` Alexander Vorobiev
2012-06-29 18:26 ` Achim Gratz
2012-06-29 19:31 ` John Hendy
2012-06-29 19:37 ` Nick Dokos
2012-06-29 20:00 ` John Hendy
2012-06-29 20:16 ` Nick Dokos
2012-07-02 20:15 ` John Hendy
2012-07-02 21:26 ` Nick Dokos
2012-07-02 21:47 ` John Hendy
2012-07-02 22:15 ` Nick Dokos
2012-07-02 22:16 ` John Hendy [this message]
2012-07-06 16:58 ` John Hendy
2012-07-06 17:12 ` Nick Dokos
2012-07-06 17:46 ` John Hendy
2012-07-06 18:41 ` Eric Schulte
2012-07-06 22:05 ` John Hendy
2012-07-06 18:45 ` Nick Dokos
2012-07-06 22:08 ` John Hendy
2012-07-06 22:14 ` John Hendy
2012-07-07 1:02 ` Eric Schulte
2012-07-07 1:48 ` Nick Dokos
2012-07-16 0:42 ` John Hendy
2012-06-30 5:13 ` Achim Gratz
2012-06-30 13:15 ` Eric Schulte
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=CA+M2ft8udMiG3j6j9rZGBHBdTuxUCoGo6AjWOih+TNOWNqofAg@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).