This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-01
Channels
- # announcements (7)
- # babashka (72)
- # beginners (62)
- # biff (1)
- # calva (9)
- # cider (8)
- # clj-kondo (35)
- # clj-otel (8)
- # cljsrn (11)
- # clojure (98)
- # clojure-europe (25)
- # clojure-germany (1)
- # clojure-norway (9)
- # clojure-uk (2)
- # clojured (3)
- # clojurescript (12)
- # conjure (3)
- # core-logic (4)
- # cursive (18)
- # datalevin (9)
- # datomic (5)
- # defnpodcast (2)
- # exercism (1)
- # graalvm (5)
- # gratitude (6)
- # hyperfiddle (3)
- # interop (12)
- # jobs (1)
- # joyride (34)
- # lsp (22)
- # meander (14)
- # missionary (16)
- # nbb (88)
- # off-topic (4)
- # pathom (20)
- # podcasts-discuss (1)
- # polylith (13)
- # portal (10)
- # re-frame (6)
- # releases (2)
- # remote-jobs (2)
- # rewrite-clj (3)
- # shadow-cljs (3)
- # spacemacs (6)
- # vim (24)
When I eval any s-expression from my nRepl client/emacs buffer it don't see the output as expected. I also don't see an Nrepl message that I would expect if the message was being correctly received. However if i save the file, then fighweel-main is correctly tracking the change and updating the browser application with the changes. Any idea how i can get client to nrepl server evalutaion back for expressions that don't require browser feedback?
Historically when this happens I believe i usually just kill my repl session and restart it, ill try that here to, but it would be nice to know why this is happening and potential avoid or fix it more gracefully.
if i try to kill the repl i'm told there is no repl in the current session. It feels like somehow the client gets dissconnected
i can't connect to it because it's already running though. which is confusing...
i think i want to connect-sibling
because i'm like a long lost brother
I'm rejected because a build is already running. Which doesn't make sense to me, i didn't want to start a new build, i wanted to join an existing session.
despite the error message/reject above, it seems my buffer/client is now correctly connected though as i can send expressions and get back results. So all is well.