From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: ocaml babel no longer works? Date: Sat, 09 Feb 2013 14:09:39 -0700 Message-ID: <876221i41q.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:58051) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4Hk2-00022L-AF for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 16:13:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U4Hjz-0000zz-Si for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 16:13:46 -0500 Received: from mail-pb0-f51.google.com ([209.85.160.51]:33635) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4Hjz-0000zs-MU for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 16:13:43 -0500 Received: by mail-pb0-f51.google.com with SMTP id un15so208116pbc.38 for ; Sat, 09 Feb 2013 13:13:42 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Alan Schmitt Cc: emacs-orgmode Alan Schmitt writes: > Alan Schmitt writes: > >> Hello, >> >> I recently updated org-mode (from git), and ocaml source code is no >> longer recognized. If I have a very simple file, like this: >> >> #+BEGIN_SRC ocaml >> let x = 2 in x >> #+END_SRC >> >> I don't get syntax highlighting, and trying to evaluate it result in an >> error: >> >> Evaluate this ocaml code block on your system? (y or n) y >> executing Ocaml code block... >> face-spec-choose: Wrong type argument: listp, class > > I have found the problem: I was missing a new line at the end of the > #+END_SRC. > > Unfortunately the evaluation of the code does not work with recent > tuareg. I first had to add: > > (defalias 'tuareg-run-caml 'tuareg-run-ocaml) > > to my configuration file. Hey Alan, Thanks for looking into this. I've applied a patch to ob-ocaml.el which should handle the two different tuareg execution functions. > But even with this it gets stuck saying "executing Ocaml code > block..." until I ctrl-G it. I'll try to see what is happening. Any > suggestion as how to debug this? > I would recommend evaluating first org-babel-execute:ocaml then possibly org-babel-prep-session:ocaml in "edebug" mode. This can be done by running `eval-defun' on these functions with a prefix argument, or equivalently doing "M-: (eval-defun t)". I would guess this is due to a change in tuareg mode. -- Eric Schulte http://cs.unm.edu/~eschulte