[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Babel R source blocks problem

From: Charles C. Berry
Subject: Re: [O] Babel R source blocks problem
Date: Sat, 28 Jan 2017 12:25:28 -0800
User-agent: Alpine 2.20 (OSX 67 2015-01-07)

On Sat, 28 Jan 2017, Thomas S. Dye wrote:

Aloha all,

I've run into a problem running R code blocks in a new Spacemacs setup.
Results are not written to the Org mode buffer.

In *Messages* I see this the first time I evaluate the R source code
Error during redisplay: (jit-lock-function 804) signaled (search-failed
"^> ")

If I run R in a :session, then I see that the source code block is
executing correctly.

Other languages don't seem to have a problem writing results to the Org
mode buffer.

Any ideas how I might debug this?

I hope somebody recognizes that message. If not, here are som suggestions:

#+NAME: alpha
#+BEGIN_SRC emacs-lisp


#+RESULTS: alpha
: abc

when you run `org-babel-execute-src-block'. Does changing "emacs-lisp"
to "R" and running again erase the result or fail to insert it if
you first run `org-babel-remove-result'?

You have already checked that C-c C-v C-i for both versions yields
identical results, right?

If so, I'd instrument `org-babel-execute-src-block', execute and then
type 'h' just before the `(org-babel-insert-result ... ' --- a couple
of lines from the bottom --- once you enter edebug. Then `e' and
`results' to see that it is what you suppose it should be. Then step
thru the next few lines to insert the result. Then check the buffer to
see what happened. If no result was inserted, then I'd instrument
`org-babel-insert-result' and work from there.



p.s. You are not trying to export this and depending on the exporter
to run babel, right? Because there is another trick lying in wait...

reply via email to

[Prev in Thread] Current Thread [Next in Thread]