[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface
From: |
Bastien |
Subject: |
Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface |
Date: |
Mon, 17 Feb 2020 00:17:28 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Hi Tim,
thanks for your email.
Tim Cross <address@hidden> writes:
> I wonder if it would make sense to use shadow-cljs rather than cider as
> a back end for evaluating clojurescript?
I am inclined to question the usefulness of evaluating ClojureScript
code *at all*.
> More generally, I wonder if there would be any benefit in considering a
> Clojure CLI Tools back end integration and bypassing CIDER altogether?
Yes, I agree this would be better.
I implemented (in master now) the support of inf-clojure.el to
evaluate Clojure blocks.
Inf-clojure is more lightweight than cider.
Also, with (setq org-babel-clojure-backend 'inf-clojure) you can now
add a :alias header arg to the src block and "clojure -Aalias" will
then be called to launch the repl.
> 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.
Yep, I agree again.
> 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.
I am not sure it is worth getting rid of inf-clojure.el altogether,
but relying on tools.deps seems the way to go.
> 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?
Definitely! Thanks for sharing these idea.
Please try the latest ob-clojure.el from master and let me know what
can be improved to better fit your (and others') needs.
Thanks,
--
Bastien
- Re: [PATCH 2/4] ob-clojure.el: Add ClojureScript interface, (continued)
- Re: [PATCH 2/4] ob-clojure.el: Add ClojureScript interface, Bastien, 2020/02/12
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, stardiviner, 2020/02/14
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, Bastien, 2020/02/14
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, stardiviner, 2020/02/14
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, Bastien, 2020/02/14
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, Tim Cross, 2020/02/14
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface,
Bastien <=
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, Tim Cross, 2020/02/16
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, Bastien, 2020/02/16
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, stardiviner, 2020/02/18
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, Bastien, 2020/02/18
- Re: [PATCH] Re: ob-clojure.el: Add ClojureScript interface, stardiviner, 2020/02/19