This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-28
Channels
- # aleph (4)
- # announcements (5)
- # babashka (28)
- # babashka-sci-dev (13)
- # beginners (63)
- # calva (76)
- # cider (113)
- # clara (7)
- # clj-kondo (42)
- # cljdoc (1)
- # clojure (170)
- # clojure-europe (20)
- # clojure-nl (17)
- # clojure-norway (3)
- # clojure-spec (12)
- # clojure-sweden (1)
- # clojure-uk (6)
- # clojurescript (55)
- # clojureverse-ops (1)
- # consulting (1)
- # core-async (9)
- # cursive (16)
- # data-science (1)
- # datascript (8)
- # datomic (27)
- # emacs (14)
- # events (1)
- # fulcro (10)
- # graphql (9)
- # gratitude (1)
- # jobs (6)
- # jobs-discuss (5)
- # leiningen (10)
- # lsp (35)
- # missionary (4)
- # nextjournal (9)
- # off-topic (46)
- # pathom (15)
- # pedestal (5)
- # polylith (37)
- # portal (15)
- # re-frame (22)
- # reagent (4)
- # reitit (5)
- # reveal (18)
- # shadow-cljs (20)
- # tools-deps (7)
- # xtdb (10)
lsp-lens enabled by default! https://github.com/emacs-lsp/lsp-mode/pull/3175
try a more windows approach rm -rf ~/.emacs.d/ && git clone --depth 1
this is a last resource that usually fixes any issue with my doom-emacs
it looks like there is a problem with nrepl
, because when I forced the version change via cider-jack-in-dependencies
, clj repl works, but cljs still doesn't
this option can help for bisecting things https://github.com/clojure-emacs/cider/blob/e52f78c54793c40ae895aa22312d71f1561897ce/cider.el#L415
As for cleaning up state between Doom updates, see https://clojurians.slack.com/archives/C0617A8PQ/p1635232231032500
the easiest way to fix it when I encounter the cider-jar
issue is just to rm -rf ~/.emacs.d/.local/straight/repos/cider ~/.emacs.d/.local/straight/build-*/cider