This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-11
Channels
- # adventofcode (116)
- # aleph (10)
- # announcements (2)
- # beginners (67)
- # boot (3)
- # calva (17)
- # cider (8)
- # cljdoc (27)
- # cljsrn (6)
- # clojure (144)
- # clojure-austin (3)
- # clojure-boston (1)
- # clojure-dev (25)
- # clojure-europe (4)
- # clojure-italy (26)
- # clojure-losangeles (4)
- # clojure-nl (28)
- # clojure-russia (1)
- # clojure-uk (34)
- # clojurescript (130)
- # cursive (20)
- # datomic (69)
- # emacs (14)
- # figwheel-main (2)
- # fulcro (31)
- # graphql (3)
- # hyperfiddle (3)
- # jobs (1)
- # jobs-discuss (1)
- # kaocha (1)
- # leiningen (2)
- # lumo (2)
- # nrepl (1)
- # off-topic (182)
- # onyx (5)
- # re-frame (88)
- # reagent (12)
- # reitit (2)
- # ring-swagger (13)
- # shadow-cljs (136)
- # tools-deps (28)
- # vim (4)
Early hours of switching a project over to deps.edn from leiningen, and new to deps tooling in general, so this could be a PEBKAC problem, but I’ve followed the cider-nrepl deps.edn instructions and running the clj command starts the NREPL server but doesn’t provide a follow-up REPL to use. It just hangs/stops after printing the NREPL host/port. Is this expected behaviour? I’m trying to add nrepl/cider so I can connect from Calva in VS Code. No issues running lein repl.
There may not be a terminal prompt after starting. The server is running though. Did connecting work?
You can to pass -i (--interactive) if you want to get a REPL as well. Generally it’s not needed if you simply want to connect to a server.
Hmm I’ll keep that in mind. I forgot that calva starts its own REPL buffer once you connect
When using figwheel-main
in cider, there're so many output from org.eclipse.jetty
in the REPL, make it really slow and unusable, is this is a problem of figwheel-main
or cider
?
@doglooksgood (setq-default bidi-display-reordering nil)
can sometimes prevent emacs performance completely tanking in the case of a lot of line-wrapping output