This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-17
Channels
- # beginners (70)
- # boot (4)
- # cider (16)
- # clara (6)
- # cljdoc (21)
- # cljs-dev (2)
- # cljsrn (1)
- # clojure (73)
- # clojure-finland (2)
- # clojure-nl (6)
- # clojure-russia (35)
- # clojure-sg (1)
- # clojure-spec (14)
- # clojure-uk (146)
- # clojurebridge (2)
- # clojurescript (128)
- # cryogen (2)
- # cursive (20)
- # datomic (27)
- # emacs (6)
- # events (8)
- # figwheel-main (57)
- # fulcro (46)
- # hoplon (3)
- # hyperfiddle (2)
- # immutant (3)
- # jobs (6)
- # jobs-discuss (15)
- # juxt (2)
- # off-topic (33)
- # parinfer (2)
- # portkey (4)
- # protorepl (1)
- # re-frame (4)
- # reagent (78)
- # ring-swagger (45)
- # schema (6)
- # shadow-cljs (167)
- # spacemacs (2)
- # specter (13)
- # tools-deps (6)
i believe there have been changes to cider recently which causes the repl session to be somewhat 'permanent' -- i can restart cider without killing the REPL now, which is a good thing. however, especially when doing stateful work, it can sometimes be desirable to get the old behavior back, where cider completely kills the JVM and re-starts a new REPL session. i was unable to find this in the docs, is this still possible?
@richiardiandrea clojure-mode doesn’t know about :style/indent
at all. Only CIDER knows about it.
There’s an nREPL middleware (named track-state) that constantly relays var metadata to CIDER and that’s used to generate at run-time dynamic indentation rules for clojure-mode
.
@lmergen Not sure what you mean. I’m assuming you’re restarting just a connection right now instead of the entire connection session.
@bozhidar yes i used to call cider-restart
which would restart the entire repl session, now it seems to be just reconnecting
Ah, I see what you mean. I’m actually not certain if now we have a command that will actually restart the server as well.
sesman-restart
will reconnect all REPLs in the session to the running nREPL server. It’s best to file a ticket for this as I’m pretty busy now and that’s something worth discussing more.
Before the new session manager I had written the code in a way that it checked if a connection was the result of a jack-in or connect. If was the result of a jack-in the server was restarted as well. Not sure how the logic about this looks right now.