Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface

[Tim Cross]

I wonder if it would make sense to use shadow-cljs rather than cider as
a back end for evaluating clojurescript?

More generally, I wonder if there would be any benefit in considering a
Clojure CLI Tools back end integration and bypassing CIDER altogether?
While I love CIDER, I'm not sure it is the right tool for a org-babel
type environment. I've recently been moving my projects from being lein
based to Clojure CLI tools based and while I still use CIDER for larger
development work, find the CLI great for basic execution of code. For
me, CIDER has a lot of additional overhead and complexity which is often
of little benefit to what I want via babel and I've found it to be a
very fragile environment. 

Sean Corfield has a great example deps.edn file at
https://github.com/seancorfield/doc-clojure and it shows how you can
hook in various different REPLs - for example, a basic socket based
REPL, which might provide a cleaner and more stable back end interface
for evaluating Clojure (and potentially clojurescript) for babel.

My rough and immature idea would be to have a back end that allowed you
to specify CLI aliases in the block header. These aliases can do a lot,
including select whatever execution environment you want the code to run
in. The back end could have default aliases for basic evaluation and it
could all be based around a socket REPL, which should make
sending/reading from the REPL fairly straight-forward. 

As I said, this is an initial and immature idea, but I think it could
provide a back end which was a little more like other babel back ends
and may be less fragile than one based on CIDER (plus I suspect it would
be faster). What do people think? Is this something worth investigating
further?

Bastien <address@hidden> writes:

> stardiviner <address@hidden> writes:
>
>> I use CIDER (sesman) keybinding =[C-c C-s d]= on ob-clojure src
>> block to link current buffer directory to CIDER REPL session.
>
> I simply start Cider with C-c M-j and then execute the Clojure source
> block with C-c C-c, it works fine.
>
>> I guess this should work for ClojureScript src block too.
>
> IMHO it works differently for ClojureScript, as C-c M-J doesn't know
> how to start a ClojureScript session unless you're in a directory with
> the proper cljs configuration (be it figwheel-main.edn, dev.cljs.edn,
> whatever.)  At least this is how I made it work.


-- 
Tim Cross