On Wed, Jul 23, 2014 at 10:08 PM, Brent Millare
wrote:
> I forgot to include in the snippet, that I would do something like
>
> (def live-repl-client (cljs.repl/channel-repl repl-env))
>
> When you say channel-repl/cider-function, do you mean
> user/live-repl-client?
>
Yes, exactly.
>
> I don'
I forgot to include in the snippet, that I would do something like
(def live-repl-client (cljs.repl/channel-repl repl-env))
When you say channel-repl/cider-function, do you mean user/live-repl-client?
I don't quite understand what you mean by (prefix).
What I want is just to be able to evaluate
Ooh, this looks interesting. Afraid I don't know enough elisp to be useful.
But it looks like you're already prompting the caller for the
*channel-repl/cider-function* name. Is there a reason you're not using it (
*prefix*) ?
Also can I ask how / where you plan to use this? Or is it just a generic
>
> As a work in progress, here is the code I came up with, it hard codes the
> function name:
>
(defun cider-eval-cljs-defun-at-point (&optional prefix)
"Evaluate the current toplevel form, and print result in the minibuffer.
With a PREFIX argument, print the result in the current buffer."
Backstory:
I modified the cljs.repl/repl to instead of pulling characters from *in*,
but to use core.async channels, and to !! out-chan
(.getMessage e))
read-error))]
(cond
(identical? f
