Fork me on GitHub
#cider
<
2019-02-20
>
dpsutton00:02:22

what's your version of lein? i believe lein 2.9.0 must use cider/piggieback "0.4.0" (if this is your problem)

oskarkv02:02:54

After cider-jack-in and "connection established", my Emacs freezes. Any ideas of what might be wrong, or how I can find out what's wrong?

soulflyer10:02:40

I was seeing something similar. I can get moving by sending emacs a kill -USR2 to drop emacs into the debugger. There are messages in the nrepl buffer (don't remember exactly what). Got round it by starting a command line repl with lein repl and doing a cider-connect-clj

dpsutton02:02:06

you can do m-x profiler-start, do some action to make it freeze up, let it freeze for a while and then run m-x profiler-report

dpsutton02:02:23

you may need some C-g in there beforehand to try to break the freeze (if possible)

oskarkv02:02:09

ok will try, thanks

dpsutton02:02:51

i'm heading out now but happy to help later

Macroz06:02:06

hmm I seem to remember that in a stacktrace in a buffer (i.e. REPL) I used to be able to RET to go to the line of code but now only clicking with mouse seems to work

robert-stuttaford10:02:31

what do i need to do to restore this behaviour? before: prns (to the default *out*) show in *cider-result* in the order that they occur, and then the evaluated result prints at the end. now: all *out* shows in the repl buffer, and only the evaluated results print in the *cider-result* buffer. Cider 21. i want the ‘before’ behaviour.

robert-stuttaford10:02:44

… and now that i typed all of that out, i’m seeing prns in cider-result!

manuel11:02:18

@christian.a.romney what problems are you experiencing? I am on latest CIDER and clj-refactor, and clj-refactor seems to be working fine (at least the features I use...)

Christian Romney12:02:21

curious do you have :pedantic? :abort set?

Christian Romney12:02:14

that could be it. because refactor-nrepl depends on nrepl 0.4.4 and cider depends on 0.6.0

Christian Romney12:02:56

let me amend that. it’s definitely why you’re not seeing the issue and I am. 🙂

manuel12:02:05

🙂 oh great

Christian Romney12:02:14

I can exclude nrepl for now and see what works

manuel12:02:32

true, but let's hope clj-refactor will be updated soon.

Christian Romney12:02:38

was just curious if anyone knew ^ right 🙂

jsa-aerial15:02:13

Any idea why setting cider-overlays-use-font-lock to either t or nil has no effect on the overlay look?

mgrbyte15:02:37

Anyone else getting errors with cider 0.21? I'm getting:

Caused by: java.lang.RuntimeException: Unable to resolve var: cider.nrepl/wrap-apropos in this context
I've got [cider/cider-nrepl "0.21.0"] in my :repl plugins section of my lein project.clj, and cider-version CIDER 0.21.0 (New York)

arohner23:02:02

I’m also seeing this behavior

arohner23:02:45

If cider-nrepl “0.21.0” or 21.1 are in my lein profile, the repl refuses to load:

Error loading cider.nrepl: Syntax error compiling at (cider/nrepl.clj:1:1).
Error loading cider.nrepl: Syntax error compiling at (cider/nrepl.clj:1:1).
Error loading cider.nrepl: Syntax error compiling at (cider/nrepl.clj:1:1).
Exception in thread "main" Syntax error compiling var at (/private/var/folders/0l/v505ws2x7x3c3nnc6yzvy0s80000gn/T/form-init5244230070535178914.clj:1:8568).
	at clojure.lang.Compiler.analyzeSeq(Compiler.java:7114)
	at clojure.lang.Compiler.analyze(Compiler.java:6789)
	at clojure.lang.Compiler.analyze(Compiler.java:6745)
	at clojure.lang.Compiler$InvokeExpr.parse(Compiler.java:3888)
	at clojure.lang.Compiler.analyzeSeq(Compiler.java:7108)
	at clojure.lang.Compiler.analyze(Compiler.java:6789)
	at clojure.lang.Compiler.analyze(Compiler.java:6745)
	at clojure.lang.Compiler$InvokeExpr.parse(Compiler.java:3888)
	at clojure.lang.Compiler.analyzeSeq(Compiler.java:7108)
	at clojure.lang.Compiler.analyze(Compiler.java:6789)
	at clojure.lang.Compiler.access$300(Compiler.java:38)
	at clojure.lang.Compiler$LetExpr$Parser.parse(Compiler.java:6384)
	at clojure.lang.Compiler.analyzeSeq(Compiler.java:7106)
	at clojure.lang.Compiler.analyze(Compiler.java:6789)
	at clojure.lang.Compiler.analyze(Compiler.java:6745)
	at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:6120)
	at clojure.lang.Compiler$FnMethod.parse(Compiler.java:5467)
	at clojure.lang.Compiler$FnExpr.parse(Compiler.java:4029)
	at clojure.lang.Compiler.analyzeSeq(Compiler.java:7104)
	at clojure.lang.Compiler.analyze(Compiler.java:6789)
	at clojure.lang.Compiler.eval(Compiler.java:7173)
	at clojure.lang.Compiler.eval(Compiler.java:7166)
	at clojure.lang.Compiler.eval(Compiler.java:7166)
	at clojure.lang.Compiler.load(Compiler.java:7635)
	at clojure.lang.Compiler.loadFile(Compiler.java:7573)
	at clojure.main$load_script.invokeStatic(main.clj:452)
	at clojure.main$init_opt.invokeStatic(main.clj:454)
	at clojure.main$init_opt.invoke(main.clj:454)
	at clojure.main$initialize.invokeStatic(main.clj:485)
	at clojure.main$null_opt.invokeStatic(main.clj:519)
	at clojure.main$null_opt.invoke(main.clj:516)
	at clojure.main$main.invokeStatic(main.clj:598)
	at clojure.main$main.doInvoke(main.clj:561)
	at clojure.lang.RestFn.applyTo(RestFn.java:137)
	at clojure.lang.Var.applyTo(Var.java:705)
	at clojure.main.main(main.java:37)
Caused by: java.lang.RuntimeException: Unable to resolve var: cider.nrepl/wrap-apropos in this context
	at clojure.lang.Util.runtimeException(Util.java:221)
	at clojure.lang.Compiler$TheVarExpr$Parser.parse(Compiler.java:720)
	at clojure.lang.Compiler.analyzeSeq(Compiler.java:7106)
	... 35 more

Michael Griffiths02:02:23

Definitely [nrepl "0.6.0"] in your deps tree as well? Does anything else depend on nrepl or cider-nrepl?

arohner14:02:27

Hrm. I depend on [cider-nrepl 0.6.0] in my ~/.lein/profiles.clj, but [nrepl "0.5.3"] is in :deps :tree, and I’m not sure why. It looks like a top-level dependency in the tree, but it’s not in profiles.clj or project.clj

Michael Griffiths16:02:46

It appears at the top level because it’s bundled by lein I think, but you should be able to force [nrepl "0.6.0"] by adding it to the :user or :dev profile (or upgrade to lein 2.9.0)

arohner11:02:51

that was it! thanks

dpsutton15:02:50

try 0.21.1 nrepl?

mgrbyte15:02:49

homer moment, sorry

mgrbyte15:02:38

helps to actually type the correct version dunit.

mgrbyte15:02:09

Well, actually, still get the same error with clj pkg [cider/cider-nrepl "0.21.1"], emacs cider-version says 0.21.0

mgrbyte15:02:28

removing cider/cider-nrepl from my :repl deps in project.clj and using cider-jack-in instead works. from the deps printed by the lein command jack-in invokes, am using same versions.

stathissideris18:02:51

hello, I have a buffer which is a clj file which is not in the classpath of the project but it contains clojure code which is valid in the contect of the project. It seems that CIDER can’t really eval statements from this file (C-c C-k is not even bound). Is there any way to “associate” such a file with a REPL?

justinbarclay18:02:37

I don’t know too much about it, I’ve never had to deal with that myself but you might want to look at CIDER + Sesman http://docs.cider.mx/en/latest/managing_connections/

stathissideris18:02:49

thanks I’ll look into it!

Christian Romney18:02:26

is there some setting to get cider to start in :init-ns? this has a history of being added and removed, so I’m not sure what the current state is. I saw a closed issue where this was resolved and wasn’t sure if it’s a regression or I’m simply unaware of the right defvar to customize. TIA

Chase19:02:51

I noticed since it went back to user ns as default the repl doesn't come with clojure.repl capability by default either anymore. is there anyway I can just always have clojure.repl doc capability? I would love that as a universal default.

Michael Griffiths20:02:11

Just pushed a fix for the :init-ns issue, sorry for the regression there. This should fix the initial namespace for Boot users also

Christian Romney16:02:58

Thank you so very much for this quick turnaround!!! Next question: I pin to melpa-stable. Will this make it into a point release e.g. 0.21.1 anytime soon?

Michael Griffiths20:02:24

@chase-lambert We should still require those by default – see the default value of cider-repl-init-code

Chase21:02:44

cool. thanks! I don't get it when starting the repl and it's in the user ns. But if I do C-c M-n M-n to change it to the core ns (which I think you were just saying you are going back to as default) I get doc functionality by default.

Michael Griffiths21:02:59

In that case it should be fixed by the latest push 😄

soulflyer10:02:40

I was seeing something similar. I can get moving by sending emacs a kill -USR2 to drop emacs into the debugger. There are messages in the nrepl buffer (don't remember exactly what). Got round it by starting a command line repl with lein repl and doing a cider-connect-clj