From: Rick Moynihan <rick.moynihan@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org, Joel Boehland <joel.boehland@evocomputing.com>
Subject: Re: Org-Babel - Clojure & Lazy Sequences Bug
Date: Fri, 26 Nov 2010 20:53:10 +0000 [thread overview]
Message-ID: <AANLkTi=mgfaAZFvY8qqf4BOcX2FTMkGdt1KqKSsTLF_d@mail.gmail.com> (raw)
In-Reply-To: <87k4jzltfi.fsf@gmail.com>
On 26 November 2010 20:29, Eric Schulte <schulte.eric@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", but have found
>> that if I do M-x slime-connect (to connect to an existing
>> clojure/swank vm) that I have access to the same vm, via the
>> *slime-repl* buffer, which is nice. Is this what you were referring
>> to, or was it something else?
>>
>
> So what I mean was execution outside of slime, e.g. by writing a code
> block to a temporary file and then executing that file with clj-env or
> some such Clojure scripting command. However the more I think about
> this the more I'm satisfied with slime, as it allows access to both
> local and remote virtual machines...
Yeah, Slime is great in this regard...
>> Having access to other sessions seems like a useful feature, but I've
>> not begun to use these more advanced babel features.
>>
>> Anyway, great work; I really appreciate you working on this!
>
> My pleasure, I use Clojure from within Org-mode files on a regular basis
> (these days I'm probably writing more Clojure than elisp), so this helps
> me too.
Well if it's your pleasure then I have another feature request for you :-)
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:
#+BEGIN_SRC emacs-lisp
(+ 10 1)
#+END_SRC
But in clojure I get:
#+begin_src clojure :results code
'(+ 10 1)
#+end_src
#+results:
| + | 10 | 1 |
I looked at implementing this myself, ontop of your recent changes, by
running it through edebug, which I've only begun to discover, but I
couldn't work it out in the hour I spent looking at it. Any
suggestions on where I should look to fix this?
R.
next prev parent reply other threads:[~2010-11-26 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 14:11 Rick Moynihan
2010-11-06 17:58 ` Eric Schulte
2010-11-24 1:51 ` Rick Moynihan
2010-11-25 17:40 ` Eric Schulte
2010-11-25 18:31 ` Rick Moynihan
2010-11-26 20:29 ` Eric Schulte
2010-11-26 20:53 ` Rick Moynihan [this message]
2010-11-26 22:49 ` Eric Schulte
2010-11-27 8:27 ` Achim Gratz
2010-11-27 15:20 ` Eric Schulte
2010-11-28 23:23 ` Rick Moynihan
2010-11-29 3:59 ` Eric Schulte
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=mgfaAZFvY8qqf4BOcX2FTMkGdt1KqKSsTLF_d@mail.gmail.com' \
--to=rick.moynihan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=joel.boehland@evocomputing.com \
--cc=schulte.eric@gmail.com \
--subject='Re: Org-Babel - Clojure & Lazy Sequences Bug' \
/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
Code repositories for project(s) associated with this inbox:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).