This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-25
Channels
- # announcements (1)
- # beginners (338)
- # calva (41)
- # cider (19)
- # cljdoc (10)
- # cljsrn (6)
- # clojure (116)
- # clojure-europe (15)
- # clojure-italy (25)
- # clojure-nl (5)
- # clojure-spec (19)
- # clojure-uk (52)
- # clojurescript (99)
- # clojurex (14)
- # cursive (47)
- # data-science (1)
- # datomic (5)
- # duct (1)
- # figwheel (13)
- # fulcro (58)
- # graalvm (93)
- # jobs (3)
- # joker (9)
- # luminus (4)
- # nrepl (21)
- # off-topic (41)
- # pathom (25)
- # re-frame (7)
- # reitit (8)
- # ring-swagger (13)
- # tools-deps (13)
@pez I’m reasonably certain that after you clone the piggieback session it goes back to being a plain nREPL session.
Inspecting the session bindings would answer this for certain. Btw, does this work for other cljs REPL types - e.g. a node or nashorn repl?
Hi all. Im running an embedded nrepl inside a mixed java/clojure project. Is there anyway to expose a user.clj or equivalent for some start/reset/stop functions?
@bozhidar: I have a feeling it might not work with nashorn, because that would explain some of the problems i ran into when trying to reproduce some funky nrepl stuff a while ago. However, it does work with lein-figwheel, Figwheel Main, and shadow-cljs, which is why I have assumed I am doing things right... (They do not revert back to plain anything.)
I think you should at least open a ticket about this on nREPL (or piggieback’s repo), so we would investigate this further at some point.
Close is supposed to clone most session bindings, but I don’t remember which one exactly.
I was certain that starting off with cloning the session you get when you connect was the way you should do it. So how does CIDER do these things?
Just pull those from the session like this https://github.com/clojure-emacs/cider-nrepl/blob/master/src/cider/nrepl/middleware/util/cljs.clj#L53
> I was certain that starting off with cloning the session you get when you connect was the way you should do it.
CIDER sets up two basic sessions for each logical connection - one for evaluations and one for everything else (aka the tooling session). The second is cloned from the first.