This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-14
Channels
- # announcements (1)
- # beginners (13)
- # calva (2)
- # cider (43)
- # cljdoc (11)
- # clojure (16)
- # clojure-spec (10)
- # clojure-uk (6)
- # clojurescript (7)
- # code-reviews (3)
- # core-matrix (1)
- # datascript (4)
- # datomic (7)
- # devcards (4)
- # figwheel-main (12)
- # fulcro (27)
- # hoplon (1)
- # lein-figwheel (1)
- # luminus (1)
- # nrepl (23)
- # off-topic (4)
- # planck (1)
- # re-frame (8)
- # reagent (7)
- # shadow-cljs (61)
- # spacemacs (7)
- # tools-deps (19)
You know what would be cool? If you could start an nrepl the same way a socket repl is started. JVM parameters. Then you would be able to: - Easily run in production, no matter the main - Jack-in on the CLJ tools wouldn't require 2 parameters for left & right of the command line. And it wouldn't interfere with any main options the user sets. Downside: - Requires writing & compiling java (but this is a large part of nrepl already)
In theory it would allow you to also jack in with lein/boot. It would ignore any boot/lein settings, that might be a good thing though 😄
I opened an issue, I think this is worth discussing https://github.com/nrepl/nREPL/issues/54
I was a bit puzzled by this part, btw. nREPL uses Java a lot via interop, but it doesn’t really have any purely Java sources. 🙂 Just as an FYI; I’m not opposed to writing some good old Java for great good.
Really. 🙂 There used to be some Java code back in the day, but it’s all gone now except for