emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: William Denton <wtd@pobox.com>
To: emacs-orgmode@gnu.org
Subject: R code blocks and 'could not find function ".ess.eval"'
Date: Tue, 28 Oct 2014 07:07:35 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1410280653400.2648@shell.miskatonic.org> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1311 bytes --]

This problem was reported last month and then again earlier this month, for 
example here:

https://lists.gnu.org/archive/html/emacs-orgmode/2014-10/msg00178.html

I'm running Emacs 25.0.50.2, Org 8.2.10 and ESS 14.1x.  I'm getting a lot of

    Error: could not find function ".ess.eval"

errors when evaluating R code blocks, even simple ones like this:

   #+BEGIN_SRC R :session :exports results
   1 + 1
   #+END_SRC

I have a more complicated Org file with a bunch of R in it that I want to export 
to a PDF, but I get this:

    Args out of range: #<killed buffer>, 0 ,1

I've been trying to debug it and seemed to narrow down a minimal example to 
whether or not a simple block had ":exports results" in it, but yesterday when 
working on this some process would go haywire and my machine would slow down 
and then freeze!  I had to force a reboot.  I've never had Emacs do that before.

I see that a patch was introduced for ob-R.el that fixes the 'could not find 
function ".ess.eval"' problem---will that be pushed into the main release soon?

And has anyone else been running into problems like this recently?  From what I 
saw in the archives it looks like it went away for most people.

Bill
-- 
William Denton ↔  Toronto, Canada ↔  https://www.miskatonic.org/

             reply	other threads:[~2014-10-28 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 11:07 William Denton [this message]
2014-10-28 16:16 ` R code blocks and 'could not find function ".ess.eval"' Charles C. Berry

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.1410280653400.2648@shell.miskatonic.org \
    --to=wtd@pobox.com \
    --cc=emacs-orgmode@gnu.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).