Eric Schulte writes:
> I think each of these patches in an improvement over the existing
> behavior. Please do apply them all.
I just applied them.
Best,
Alan
Alan Schmitt writes:
> Hello,
>
> I'm resurrecting this old thread as I've made some progress but I
> still have questions.
>
> Eric Schulte writes:
>
>>> The suggestion: instead of appending '"org-babel-ocaml-eoe";;' to the
>>> code, how simply put ';;' (which will make sure everything is flushe
Hello,
I've been using this patch for the last few days and I have not found
any issue with it. Can I apply it?
Thanks,
Alan
Alan Schmitt writes:
> Hello,
>
> I'm resurrecting this old thread as I've made some progress but I
> still have questions.
>
> Eric Schulte writes:
>
>>> The suggestion
Hello,
I'm resurrecting this old thread as I've made some progress but I
still have questions.
Eric Schulte writes:
>> The suggestion: instead of appending '"org-babel-ocaml-eoe";;' to the
>> code, how simply put ';;' (which will make sure everything is flushed)
>> then detect the toplevel is do
Alan Schmitt writes:
> Hi Eric,
>
> Eric Schulte writes:
>
>>> The suggestion: instead of appending '"org-babel-ocaml-eoe";;' to the
>>> code, how simply put ';;' (which will make sure everything is flushed)
>>> then detect the toplevel is done by seeing the string '# ' at the
>>> beginning of th
Hi Eric,
Eric Schulte writes:
>> The suggestion: instead of appending '"org-babel-ocaml-eoe";;' to the
>> code, how simply put ';;' (which will make sure everything is flushed)
>> then detect the toplevel is done by seeing the string '# ' at the
>> beginning of the line? Would there be an issue w
Alan Schmitt writes:
> Hello,
>
> Eric Schulte writes:
>
>> Thanks for looking into this. I've applied a patch to ob-ocaml.el which
>> should handle the two different tuareg execution functions.
>
> Thanks a lot.
>
> About the thing "getting stuck", I made some progress. My error was that
> I di
Hello,
Eric Schulte writes:
> Thanks for looking into this. I've applied a patch to ob-ocaml.el which
> should handle the two different tuareg execution functions.
Thanks a lot.
About the thing "getting stuck", I made some progress. My error was that
I did not add ";;" at the end of my ocaml p
Hi Eric,
Eric Schulte wrote:
> Alan Schmitt writes:
>> 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)
>>
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
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
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
12 matches
Mail list logo
