Fork me on GitHub
#cider
<
2019-02-21
>
yuhan01:02:03

Anyone else here using CIDER with lispy?

☝️ 2
yuhan01:02:31

I recently noticed a few bugs with using lispy-eval, curious to know if other people are experiencing the same issues: https://github.com/abo-abo/lispy/issues/478

aisamu03:02:05

not seeing this here with

;; CIDER 0.21.0snapshot (package: 20190125.1339), nREPL 0.6.0

yuhan03:02:49

Are you also on the latest version of lispy? And none of the above 4 issues are present on your end?

danieroux07:02:40

I've updated the issue @UCPS050BV, I see the same issues.

danieroux07:02:09

This is what REBL tracks. The first one is cider-eval-last-sexp, and the second one is special-lispy-eval

aisamu08:02:25

Is that something I could query to get lispy's version? The elpa folder is lispy-20190206.1632, and inspecting the source I found ;; Version: 0.26.0. This is being fetched by lispyville, but the use-package contains no version info, so I assume it's pointing to the latest.

yuhan09:02:50

@U9E8C7QRJ Thanks for the confirmation! I was afraid it was something in my configuration. Using REBL to track the values is an interesting idea, I tried briefly to hunt down the source of the errors using Edebug but there doesn't seem to be an easy way to set breakpoints or inspect values once the string is passed over to the lispy-clojure.clj side of things.

yuhan09:02:26

@U1UQEM078 That looks like the latest version, are you sure that you are using M-x lispy-eval or "e" in a special position to execute the forms as opposed to the cider-eval-* commands?

aisamu09:02:36

Yup, checked that! (And just retried)

aisamu09:02:06

Also tried calling lispy-eval directly, same. (Unless it's being monkey-patched with something else? I use lispyville)

yuhan09:02:48

hmm.. I use lispyville too, as far as I know there's nothing overriding or advising the lispy-eval functions

😕 1
yuhan10:02:52

I'm testing this on clojure 1.10 , Mac OS 10.14, Emacs 26.1 with a empty deps.edn project, in case that's relevant

yuhan10:02:45

also tried with a lein project and clojure 1.90, 1.70 - same results

aisamu12:02:10

The REPL is running on Linux, Clojure 1.9.0 with Shadow-cljs (2.7.xx). Emacs is 25.3.1 on OSX 10.10.5 (I know, I know)

dpsutton13:02:54

if you want to watch the CIDER wire try m-x nrepl-toggle-message-logging and then you'll find a *messages-[connection-name]-* buffer with the messages to and from nrepl

👏 1
kommen09:02:15

I also see similar errors sometimes:

kommen09:02:17

Caused by: java.lang.RuntimeException: No such var: stacktrace/analyze-causes
	at clojure.lang.Util.runtimeException(Util.java:221)
	at clojure.lang.Compiler.resolveIn(Compiler.java:7387)
	at clojure.lang.Compiler.resolve(Compiler.java:7357)
	at clojure.lang.Compiler.analyzeSymbol(Compiler.java:7318)
	at clojure.lang.Compiler.analyze(Compiler.java:6768)
	... 104 more

kommen09:02:53

they go away when I just start the clojure process again

kommen09:02:16

this is cider 0.21.1 with piggyback 0.4 and nrepl 0.6