This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-18
Channels
- # adventofcode (326)
- # aws (1)
- # beginners (67)
- # cider (52)
- # cljs-dev (5)
- # cljsrn (5)
- # clojure (104)
- # clojure-art (2)
- # clojure-austin (34)
- # clojure-france (12)
- # clojure-greece (38)
- # clojure-india (2)
- # clojure-italy (6)
- # clojure-spec (11)
- # clojure-uk (32)
- # clojurescript (51)
- # core-async (5)
- # cursive (11)
- # data-science (5)
- # datascript (3)
- # datomic (3)
- # defnpodcast (7)
- # fulcro (26)
- # graphql (10)
- # hoplon (1)
- # instaparse (2)
- # jobs (1)
- # klipse (3)
- # lumo (13)
- # off-topic (50)
- # om (2)
- # onyx (19)
- # parinfer (1)
- # pedestal (4)
- # re-frame (18)
- # ring-swagger (1)
- # spacemacs (1)
- # specter (42)
- # sql (9)
- # uncomplicate (18)
- # unrepl (13)
So, you can dynamically load libraries in the running REPL I presume? That’s interesting. It’s possible with nREPL to some extent, but it’s a bit painful that’s why I opted not to support it directly in CIDER. At least it used to be painful. 🙂
Yes. It’s used in 2 ways: to load additional nrepl actions and to load user code (both in jars or local files in durs). So you can load and reload a local ns from a remote server.
The client may choose to have multiple auxs if some tooling actions are long and blocking.
This thread should be of interest to this channel: https://clojureverse.org/t/share-the-nitty-gritty-details-of-your-clojure-workflow/1208
I was going through clojureD lightning talks and saw this: https://github.com/AvramRobert/omnia a terminal base REPL, it seems to have some good features implemented, might be interested to look at
Looks cool for sure
Definitely