This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-02
Channels
- # beginners (29)
- # cider (41)
- # clara (1)
- # cljs-dev (17)
- # cljsrn (1)
- # clojure (158)
- # clojure-dev (2)
- # clojure-dusseldorf (2)
- # clojure-italy (8)
- # clojure-mexico (1)
- # clojure-russia (2)
- # clojure-spec (43)
- # clojure-uk (1)
- # clojurescript (44)
- # community-development (98)
- # cursive (9)
- # data-science (8)
- # datascript (4)
- # datomic (30)
- # emacs (6)
- # fulcro (11)
- # graphql (6)
- # jobs (1)
- # jobs-discuss (27)
- # lein-figwheel (5)
- # luminus (13)
- # lumo (4)
- # off-topic (28)
- # onyx (9)
- # parinfer (12)
- # perun (2)
- # portkey (5)
- # re-frame (48)
- # ring (2)
- # shadow-cljs (52)
- # spacemacs (29)
- # tools-deps (15)
- # unrepl (9)
- # vim (7)
- # yada (3)
When I use cider-jack-in
in emacs, I get this message instead,
;; Connected to nREPL server -
;; CIDER 0.16.0 (Riga), nREPL 0.2.13
;; Clojure 1.8.0, Java 9.0.1
...which is what I'm expecting with lein repl
@fedreg Are you using spacemacs main repo or develop? I'm using develop and I can't get the new clojure.repl to work via cider-jack-in because sayid middleware is not compatible and breaks things. I disabled the package and it works. Just putting that out there in case your problem is related.
@pauld I use the main repo; but this problem was not with spacemacs. Cider works great with spacemacs. I'm having this issue with vanilla emacs.
@dominicm I don’t remember something like this. There was just a conversation as to whether orchard should know about piggieback, and I believe it shouldn’t as that’s a definitely an nREPL concern.
@weslord No, the expectation is not correct. CIDER’s REPL prints a custom message, that you would not get using lein repl
. Btw, modifying the profiles is not needed at all these days.
Thanks. I'm setting up vim-fireplace, and since it "mostly works" without cider-nrepl, I can't tell if it is using it or not.
I should probably just take a "no news is good news" approach to this for now and stop looking for problems.
> @fedreg Are you using spacemacs main repo or develop? I’m using develop and I can’t get the new clojure.repl to work via cider-jack-in because sayid middleware is not compatible and breaks things. I disabled the package and it works. Just putting that out there in case your problem is related.
> @pauld I use the main repo; but this problem was not with spacemacs. Cider works great with spacemacs. I’m having this issue with vanilla emacs.
@fedreg What problems exactly are you having? I’m using vanilla Emacs and everything’s just fine (as it should be 🙂 ).
Interesting. I’d suggest consulting the troubloshooting section of the manual to track down what’s going wrong.
@bozhidar Thanks! Turned off evil-mode and is working fine now. There must be some sort of binding conflict. Will have to investigate a bit. Thanks for the help (and the debugger!!)!
That’s one of the tricky parts about editors like Emacs and Vim - there are often weird interactions between some of the packages people might be using. 🙂
@thheller Can you remind me what was the form needed to start a cljs REPL? (I’m too lazy to go over the manual) 🙂 I want to add this soon, so I can wrap the phase one of proper shadow-cljs support.
@bozhidar its not a single form since it depends on which REPL we are talking about. (shadow.cljs.devtools.api/node-repl)
or (../browser-repl)
or (../nrepl-select <the-build-id-keyword>)
. didn't add the no-arg nrepl-select
yet.
Regarding the nrepl-select
version I’m planning to just ask users to provide the build themselves before starting it, which is a reasonable compromise imo.
I’m just a bit confused why some repls don’t require a build id and so do. I guess I really need to educate myself better on the subject.
@bozhidar This is what I get in spacemacs develop branch when I try to jack into a clojure.repl project with sayid as part of the middleware installed:
can someone try to reproduce this issue? https://github.com/clojure-emacs/cider/issues/2254
It's very simple. Just turn on logging and cider-jack-in
. I'm getting some strange output in the logging buffer and trying to determine if its something weird on my end or in the message logging
I guess spacemacs enables clj-refactor.el out of the box or something like this. Most likely you’re running a version of refactor-nrepl, that’s not compatible with cider-nrepl.
(defun cider--debug-init-connection ()
"Initialize a connection with the cider.debug middleware."
(cider-nrepl-send-request
(nconc '("op" "init-debugger")
(when cider-debug-print-level
`("print-level" ,cider-debug-print-level))
(when cider-debug-print-length
`("print-length" ,cider-debug-print-length)))
#'cider--debug-response-handler))
Thanks for confirming. I looked into it and the messages coming into the log printer looked right. I think it's strictly on the logging side
I fail to see how this message is different from any other message, though. Why aren’t we getting such problems elsewhere?
No idea. But stepping through, the msg parameter did not have the duplicates as far as I could tell
i really like the :style/indent
for making marco indent work for the devs in my team. I recalled watching "Clojure: The Bad Parts" about not having a standard for indentation -- was there a discussion of this at some point (with the other tools out there, i.e. cljfmt), i'd love to have this work automatically for all-the-tools, since some folks at work don't use cider/emacs