This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-09
Channels
- # announcements (4)
- # beginners (44)
- # boot (15)
- # calva (66)
- # cider (66)
- # clojure (75)
- # clojure-austin (4)
- # clojure-europe (2)
- # clojure-finland (1)
- # clojure-italy (3)
- # clojure-nl (10)
- # clojure-russia (3)
- # clojure-sg (1)
- # clojure-uk (109)
- # clojurescript (18)
- # datomic (8)
- # emacs (1)
- # figwheel-main (1)
- # fulcro (5)
- # jobs (1)
- # jobs-discuss (8)
- # kaocha (7)
- # leiningen (11)
- # luminus (2)
- # off-topic (69)
- # pathom (5)
- # re-frame (7)
- # reagent (4)
- # reitit (18)
- # ring-swagger (3)
- # shadow-cljs (123)
- # spacemacs (1)
- # sql (35)
- # tools-deps (89)
- # uncomplicate (3)
- # vim (6)
- # yada (3)
Any tips for how to investigate a sudden onset of nREPL: [Errno 61] Connection refused^@
when trying to evaluate a form using vim-fireplace? It was working this morning, and now, .. not. The REPL is on a virtualbox (managed with vagrant). I've restarted everything from scratch, laptop, machines, flushed dns caches. I can connect to the repl using lein repl :connect my.internal.url:[my port]
. It just doesn't seem to want to work from within vim
I had my laptop seize up earlier today which I suspect is the cause, but I'm confused why it'll work from the command line using lein repl :connect
but not within vim
Are you connecting using :Connect or relying on fireplace figuring out the port by reading the .nrepl-port file?