Eric Schulte writes:
This looks great, please apply this patch.
Done.
Alan
Hello,
I just applied a small bugfix for this: it seems that the first time the
toplevel is started, something is mixed up in the buffers and the first
exported result end up in the toplevel buffer instead of the export
buffer. I put back the `save-window-excursion' around the code that
starts
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello,
I just applied a small bugfix for this: it seems that the first time the
toplevel is started, something is mixed up in the buffers and the first
exported result end up in the toplevel buffer instead of the export
buffer. I put back
Hello,
Can I apply this patch?
Thanks,
Alan
Alan Schmitt writes:
Hello,
It is not currently possible to asynchronously export the results of the
evaluation an ocaml babel block because the evaluation needs to start a
toplevel
and thus asks the user what program to run. This of course
This looks great, please apply this patch.
Thanks,
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello,
It is not currently possible to asynchronously export the results of the
evaluation an ocaml babel block because the evaluation needs to start a
toplevel
and thus asks the user
Hello,
It is not currently possible to asynchronously export the results of the
evaluation an ocaml babel block because the evaluation needs to start a toplevel
and thus asks the user what program to run. This of course blocks the
asynchronous export.
The attached patch adds a custom variable to
