This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-27
Channels
- # beginners (54)
- # bitcoin (2)
- # boot (1)
- # calva (10)
- # cider (30)
- # cljs-dev (25)
- # cljsrn (17)
- # clojure (27)
- # clojure-dev (16)
- # clojure-estonia (3)
- # clojure-hk (1)
- # clojure-italy (8)
- # clojure-losangeles (1)
- # clojure-nl (17)
- # clojure-russia (1)
- # clojure-spec (15)
- # clojure-uk (45)
- # clojurebridge (1)
- # clojurescript (95)
- # clojurescript-ios (1)
- # core-async (5)
- # cursive (10)
- # datomic (8)
- # emacs (2)
- # figwheel-main (31)
- # fulcro (99)
- # hyperfiddle (3)
- # immutant (1)
- # jobs (13)
- # jobs-discuss (82)
- # keechma (6)
- # leiningen (3)
- # lumo (1)
- # nrepl (1)
- # off-topic (37)
- # onyx (1)
- # pedestal (6)
- # re-frame (7)
- # reitit (2)
- # remote-jobs (1)
- # ring-swagger (3)
- # rum (6)
- # shadow-cljs (14)
- # specter (4)
- # tools-deps (27)
- # yada (12)
hey 👋 I’m wondering if there’s an obvious reason I’m missing for prompts like https://github.com/clojure-emacs/cider/issues/2444#issuecomment-423757742 to exist? I feel it would be much nicer if cider just reconnected without a prompt.
we have our app setup so it automatically connects cider on boot. So when I kill the app via ctrl+c
and restart it I get the prompt. Is there any way to recover state from a dead repl or what’s the reasoning behind that prompt? When would I not want to say yes to this?
@mkvlr We can’t recover the REPL state, but you get to keep the history in the REPL buffer, which some people find useful.
Obviously we can just add some switch to disregard the REPL buffer similarity and directly reconnect (as it was before this patch).
If you kill the nREPL server the state disappears with it. If you just re-connect the state will stay around.
Btw, is your problem with the fact we try to reuse the dead REPL buffer or with the fact that we display a prompt?
I believe there’s also a bug in 0.18 that resulted in everything breaking when connecting a second repl but I think that’s fixed now
would you be open to a PR either introducing a setting or automatically reusing the buffer without a prompt?
Got it. Just keep in mind that match might not be exact, which is the main reason there’s a prompt. If you have just one repl buffer obviously that’s not a real concern, though.
Quickly searching through CIDER settings I think it’s cider-auto-jump-to-error
If someone’s interested in auth support for nREPL they can check out https://github.com/nrepl/nREPL/pull/46