From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: I need help extending ob-ocaml to support :results output
Date: Mon, 24 Mar 2014 13:45:31 +0100 [thread overview]
Message-ID: <m2vbv3zrx0.fsf@polytechnique.org> (raw)
In-Reply-To: <87vbv4gxzl.fsf@gmail.com> (Eric Schulte's message of "Sun, 23 Mar 2014 19:50:54 -0600")
Eric Schulte <schulte.eric@gmail.com> writes:
> You can step through the execution of `org-babel-execute:ocaml' by first
> evaluating the function with a prefix argument (meaning with the cursor
> within the function body press C-u C-A-x) which will edebug [1] the
> function.
>
> You can then evaluate an OCaml code block and when execution hits the
> `org-babel-execute:ocaml' it will pause, and you can step through the
> function by continuously pressing space bar. In this way you can see
> how the code is executed, and you can interactively look at the OCaml
> session buffer to see where output is printed. Pay special attention to
> the `org-babel-comint-with-output' function, which is probably where
> you'll need to make changes when the following holds.
>
> (member "output" (cdr (assoc :result-params params)))
>
> You can also look for the string "output" in other ob-*.el language
> files to see how output results are collected.
>
> Hope this helps,
It does, thanks a lot.
Alan
next prev parent reply other threads:[~2014-03-24 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 16:35 I need help extending ob-ocaml to support :results output Alan Schmitt
2014-03-24 1:50 ` Eric Schulte
2014-03-24 12:45 ` Alan Schmitt [this message]
2014-03-26 21:39 ` Alan Schmitt
2014-03-29 11:07 ` Alan Schmitt
2014-03-29 11:26 ` Bastien
2014-03-29 14:03 ` Nicolas Goaziou
2014-03-29 18:23 ` Alan Schmitt
2014-03-29 18:43 ` Nicolas Goaziou
2014-03-29 18:52 ` Alan Schmitt
2014-03-29 19:08 ` Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2vbv3zrx0.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.