This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-09
Channels
- # announcements (16)
- # babashka (28)
- # beginners (27)
- # calva (39)
- # chlorine-clover (6)
- # cider (8)
- # clara (28)
- # cljs-dev (19)
- # cljsrn (22)
- # clojure (78)
- # clojure-australia (3)
- # clojure-europe (64)
- # clojure-nl (3)
- # clojure-norway (14)
- # clojure-spec (2)
- # clojure-uk (11)
- # clojurescript (11)
- # core-async (24)
- # datomic (3)
- # deps-new (5)
- # emacs (9)
- # fulcro (4)
- # gis (2)
- # graalvm (9)
- # honeysql (2)
- # hoplon (5)
- # instaparse (1)
- # introduce-yourself (5)
- # jobs (5)
- # luminus (4)
- # observability (7)
- # off-topic (6)
- # pathom (18)
- # pedestal (5)
- # polylith (4)
- # re-frame (2)
- # reagent (1)
- # reitit (1)
- # remote-jobs (7)
- # shadow-cljs (47)
- # specter (1)
- # sql (27)
- # testing (6)
- # tools-deps (4)
- # vim (3)
- # xtdb (8)
Hi @mauricio.szabo, I’m using Clover (thanks for making this great extension!), but sometimes I see error messages with nrepl
in it. I suspect some of my dev tooling starts an nrepl somewhere, but I’m pretty sure I’m connecting to the correct port number for the socket repl. Is there a command I can run to verify I’m using a socket repl?
Hi, @jlmr, yes, if you are running a Clojure REPL and want to check, evaluate (range 2000)
. It will not print the full collection
(can you give me an example of the nrepl errors you're having? I want Chlorine to work with nREPL too, so this may be an issue that I have to target 🙂 )
Unfortunately I already cleared the repl and fixed the bug, so I’m not sure what the error was exactly. If it occurs again I’ll post it here
Thanks 🙂. The existence of an nREPL running should not be a problem (I use Chlorine with lein everyday, so everytime I have nREPL running too), but we never know :rolling_on_the_floor_laughing: