This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-03-20
Channels
- # announcements (5)
- # aws (15)
- # babashka (12)
- # beginners (87)
- # calva (13)
- # cider (16)
- # clj-kondo (4)
- # clojure (22)
- # clojure-argentina (1)
- # clojure-europe (9)
- # clojure-houston (1)
- # clojure-nl (2)
- # clojure-norway (25)
- # clojure-uk (5)
- # clojurescript (12)
- # core-typed (37)
- # cursive (15)
- # datomic (40)
- # editors (8)
- # emacs (4)
- # events (1)
- # hyperfiddle (29)
- # keechma (8)
- # leiningen (6)
- # lsp (7)
- # malli (25)
- # off-topic (26)
- # pathom (10)
- # portal (3)
- # re-frame (22)
- # reitit (1)
- # releases (1)
- # ring (2)
- # shadow-cljs (18)
- # yamlscript (1)
Has anyone had the same issue that I'm having now with Emacs + org-mode while attempting to tangle Clojure code? Tangling any clojure source block results in the expression to be wrapped with something like this (in this case the source block having (+ 1 2 3) in it:
(prn (binding [*out* (java.io.StringWriter.)](+ 1 2 3)))Yes, I had this issue. I found that line in ob-clojure.el and removed it
I forgot to tell you I solved it by just defining ":eval no" in the header args.. but it is kinda funny it tries to both eval it at the time of tangling.. IIRC other babel languages don't do that.. I wonder if that should be considered as a bug/oversight that should be fixed in ob-clojure?
That's good to know. I usually set :eval yes on most of my blocks so I can develop interactively. I haven't noticed the behavior in any other babel languages either, so I think it probably is an oversight.