This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-27
Channels
- # bangalore-clj (1)
- # beginners (11)
- # boot (23)
- # business (2)
- # cider (43)
- # cljs-dev (65)
- # cljsjs (17)
- # cljsrn (4)
- # clojure (144)
- # clojure-austin (4)
- # clojure-berlin (3)
- # clojure-finland (4)
- # clojure-nl (2)
- # clojure-russia (13)
- # clojure-spec (73)
- # clojure-uk (42)
- # clojured (2)
- # clojurescript (166)
- # core-matrix (4)
- # cursive (24)
- # datomic (39)
- # dirac (8)
- # hoplon (97)
- # jobs (2)
- # jobs-rus (11)
- # juxt (16)
- # lein-figwheel (8)
- # leiningen (1)
- # luminus (5)
- # lumo (46)
- # off-topic (1)
- # om (39)
- # onyx (43)
- # overtone (1)
- # pedestal (3)
- # perun (6)
- # play-clj (3)
- # protorepl (14)
- # re-frame (21)
- # reagent (25)
- # remote-jobs (1)
- # ring (1)
- # robots (4)
- # rum (13)
- # specter (5)
- # untangled (72)
- # yada (62)
@hans @pesterhazy I’ll see what we can do to improve the situation in CIDER, but it seems to me that nREPL will need to be patched as well
I seemed to have really messed up my setup this time... does this sound familiar to anyone? When I cider-jack-in
, a prompt pops up in the minibuffer saying Lisp expression:
Debugger entered--Lisp error: (error "Not an nREPL dict object: (+ 1 1)")
signal(error ("Not an nREPL dict object: (+ 1 1)"))
error("Not an nREPL dict object: %s" (+ 1 1))
nrepl-dict-get((+ 1 1) "interns")
cider-resolve-ns-symbols((+ 1 1))
cider-refresh-dynamic-font-lock((+ 1 1))
cider-set-buffer-ns((+ 1 1))
cider-repl-set-initial-ns(#<buffer *cider-repl App*>)
cider-repl-init(#<buffer *cider-repl App*>)
cider--connected-handler()
run-hooks(nrepl-connected-hook)
nrepl-start-client-process(nil 42389 #<process nrepl-server>)
nrepl-server-filter(#<process nrepl-server> "nREPL server started on port 42389 on host 127.0.0.1 - )
WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: mranderson047.toolsanalyzerjvm.v0v6v9.toolsanalyzer.v0v6v7.clojure.tools.analyzer.utils, being replaced by: #'mranderson047.toolsanalyzerjvm.v0v6v9.toolsanalyzer.v0v6v7.clojure.tools.analyzer.utils/boolean?
WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: mranderson047.toolsanalyzerjvm.v0v6v9.toolsanalyzer.v0v6v7.clojure.tools.analyzer, being replaced by: #'mranderson047.toolsanalyzerjvm.v0v6v9.toolsanalyzer.v0v6v7.clojure.tools.analyzer.utils/boolean?
nREPL server started on port 42389 on host 127.0.0.1 -
(-->
op "eval"
code "(str *ns*)"
enlighten "true"
session "b72d41fa-6418-441f-bc52-cc8e7138c986"
id "4"
)
(<--
ex "class java.lang.Exception"
id "4"
root-ex "class java.lang.Exception"
session "b72d41fa-6418-441f-bc52-cc8e7138c986"
status ("eval-error")
)
(<--
err "Exception Debugger not initialized user/eval27659/fn--27660 (form-init2222324724219143458.clj:1)
"
id "4"
session "b72d41fa-6418-441f-bc52-cc8e7138c986"
)
ugh I remember having that issue a while ago but can’t remember how it got resolved… what versions are you using?
I thought it was something with my project, but went back to an older commit that should be good and still getting this. same on a different project... cleaned out all generated files (git clean -xfd), nuked ~/.m2, rebooted emacs...
is there a way to not have two repls start up with a cider-jack-in-clojurescript
command. I don't want the clj repl only the cljs repl.
@dpsutton a desktop file is emacs way of storing and restoring state like open buffers between restarts
looking through it it seems it had cider-enlighten-mode enabled in a bunch of buffers, that's the most likely culprit
Has anyone tried to do any debugging of breakpoints in Java code that was invoked from Clojure in the REPL when using Emacs/Cider?
I know Cider has a Clojure-centric (and nice) debugger, however, what about when you are interop’ing with Java libs and want to see what is going on there with a “traditional” style of Java debugging.
@hans, I don't think contrib projects take PRs, as a rule