Hey Rick,
Rick Moynihan rick.moyni...@gmail.com writes:
Hey Eric,
I've just run your ob-clojure, and it seems to work fine, though as
you mention it would be nice if it'd start slime (if it isn't already
running).
Alright, I'm going to fold this into the master branch (we'll still have
On 26 November 2010 20:29, Eric Schulte schulte.e...@gmail.com wrote:
Alright, I'm going to fold this into the master branch (we'll still have
the entirety of the existing ob-clojure in git for resurrection if need
be).
That's great news!
I'm not sure what you mean by external evaluation,
Rick Moynihan rick.moyni...@gmail.com writes:
Basically it looks like the different :results types haven't yet been
implemented... The one I was missing was 'code' e.g. the following
works for elisp:
#+begin_src emacs-lisp :results code
'(+ 10 1)
#+end_src
displaying:
#+results:
Hi Rick,
I'm not quite sure what the best permanent solution would be. I'm
tempted to switch to a drastically stripped down version of Clojure
interaction which relies very heavily on slime. I'm attaching a first
pass at this which allows for slime-based execution, can assign
variables, handles
Hey Eric,
I've just run your ob-clojure, and it seems to work fine, though as
you mention it would be nice if it'd start slime (if it isn't already
running).
I'm not sure what you mean by external evaluation, but have found
that if I do M-x slime-connect (to connect to an existing
clojure/swank
Hi Rick,
I've noticed this as well. I'm not the original author of ob-clojure.el
(Joel Boehland is), so I'm not sure how the clojure interaction
currently works, although I know it makes heavy usage of slime. There
must be an existing mechanism used by slime to unroll these lazy
evaluations,
I have the following org file:
#+BEGIN_SRC clojure
(range 10)
#+END_SRC
#+results:
: clojure.lang.lazy...@f35bf8c6
Where as I would expect to see the sequence. Evaluating the code
inside a doall doesn't seem to do anything either:
#+BEGIN_SRC clojure
(doall (range 10))
#+END_SRC
#+results:
:
