This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-17
Channels
- # beginners (52)
- # boot (116)
- # cider (21)
- # cljs-dev (44)
- # clojure (104)
- # clojure-dev (82)
- # clojure-greece (5)
- # clojure-japan (4)
- # clojure-nl (14)
- # clojure-russia (65)
- # clojure-serbia (3)
- # clojure-spec (38)
- # clojure-uk (9)
- # clojure-ukraine (1)
- # clojurescript (65)
- # clojurewest (1)
- # community-development (1)
- # core-logic (3)
- # cursive (5)
- # data-science (9)
- # datomic (13)
- # emacs (45)
- # euroclojure (1)
- # hoplon (2)
- # instaparse (23)
- # javascript (1)
- # jobs (2)
- # klipse (43)
- # leiningen (8)
- # lumo (25)
- # off-topic (7)
- # om (13)
- # om-next (3)
- # onyx (11)
- # pedestal (12)
- # planck (19)
- # proton (1)
- # re-frame (26)
- # reagent (26)
- # remote-jobs (13)
- # ring-swagger (23)
- # spacemacs (1)
- # untangled (3)
Bug report : from clojurescript 1.9.456 onward, the destructure of map malfunctioned just in cider REPL, like this:
(let [{a :a} {:a 3}] a
in REPL, it returns nil
in 1.9.229 it works as expected
Hi! I keep seeing
error in process filter: [nREPL] Direct connection failed
when using M-x cider-jack-in
. I've always had this problem, but most of the times it just went away when I try to jack in once more. On the machine I'm working on now, though, it takes many attempts until I get a repl running. It seems that there is a lingering bug somewhere deep down, what can I do to help tracking it down?Q: I have both repls in project (CLJ and CLJS). Where is the setting which will force using CLJS repl for .cljc files? Or it is not configurable now?
Ok hacking cider internals helped.
+++ (setq cider-use-clj-repl-for-cljs nil)
(defun cider-connection-type-for-buffer ()
"Return the matching connection type (clj or cljs) for the current buffer.”
(cond
+++ ((derived-mode-p 'clojurec-mode) (if cider-use-clj-repl-for-cljs "clj" “cljs”))
((derived-mode-p 'clojurescript-mode) “cljs”)
((derived-mode-p 'clojure-mode) “clj”)
(cider-repl-type)
(t "clj")))
If anyone know better way to same thing, please share@hans, much better to open the repl in a separate terminal window, then cider-connect
then you see all the problems pop up in the terminal window
plus it's always a good idea to check the *cider nrep...
buffer
@pesterhazy I like to see problems pop up in the *cider-nrepl*
buffer, and I like to work from within emacs rather than having a separate terminal window open.
@pesterhazy Like, I would like to help fixing this bug rather than changing how I work to work around it.
and that's a good idea. To debug, I would run the repl in a separate terminal window and see if that works 🙂
and you can connect from cider?
ok so in all probability there's a difference between the way cider starts lein/boot and the way you start it manually
or maybe it just takes too long and cider gives up?
There are no error messages in the nrepl buffer. And if I repeat the attempt often enough, it succeeds. It has been a problem for years, really.
if you suspect something is wrong with your cider, you could try deleting all cider related packages from ~/.emacs.d/elpa
and restart
it could also be about the cider middleware used
perhaps related to your lein profile