This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-05
Channels
- # beginners (53)
- # boot (6)
- # braveandtrue (12)
- # cider (50)
- # cljs-dev (24)
- # clojure (60)
- # clojure-finland (1)
- # clojure-ireland (1)
- # clojure-italy (50)
- # clojure-kc (1)
- # clojure-nl (20)
- # clojure-norway (1)
- # clojure-portugal (1)
- # clojure-russia (2)
- # clojure-sanfrancisco (1)
- # clojure-sweden (1)
- # clojure-uk (176)
- # clojurescript (58)
- # cursive (14)
- # datomic (23)
- # emacs (4)
- # events (16)
- # fulcro (35)
- # graphql (48)
- # hyperfiddle (9)
- # jobs (5)
- # mount (4)
- # onyx (13)
- # overtone (1)
- # play-clj (2)
- # re-frame (91)
- # reagent (9)
- # reitit (9)
- # shadow-cljs (102)
- # sql (3)
- # testing (3)
- # tools-deps (3)
Just a quick FYI - the nasty problem with cider-test.el
is finally fixed. This time - for real. 😉
Do I have to do something special to get expound to work with a CIDER-started REPL? I haven’t been able to get it to work.
Also, I’m using io.aviso/pretty
and it works on the actual REPL output, but not on the *cider-error*
buffer.
> Do I have to do something special to get expound to work with a CIDER-started REPL? I haven’t been able to get it to work.
No idea how this works. Explaining the problems you’ve got with it would be helpful.
> Also, I’m using io.aviso/pretty
and it works on the actual REPL output, but not on the *cider-error*
buffer.
Because this buffer is now a raw rendering of the stracktrace, but it’s custom built by CIDER.
I think we had some setting to just display the raw stacktrace, but I don’t remember it off the top of my head.
It could be I’m misunderstanding how expound works, but I think it taps into the clojure.spec
*explain-out*
function. You are supposed to set it up either with a binding, or by using alter-var-root
to bind *explain-out*
for all the threads. I’ve never seen this in action, so I don’t know if this is a lein
issue or a CIDER
issue.
I’m only asking here just in case it’s a known thing with CIDER — if it’s not common then please don’t waste time, I’ll debug it on my own, as it could be just some weird project setup I have here.
Thanks for the navigating stacktraces link — I can see it’s very powerful, I had no idea.
@orestis I have used expound and calls to 'expound/expound' have worked without a hitch
@dpsutton Thanks for the vote of confidence. What about Compiler Exceptions? I was expecting that those would be formatted using *explain-out*
as well, but perhaps I’m misunderstanding.
I'd appreciate it if you let me know what you discover
That also happened to me, but I didn't have time yet to understand what was going on
using expound/expound
directly works fine, but binding *explain-out*
doesn't :thinking_face:
i've never tried hooking it into the spec apparatus like you are trying to do unfortunately. I've only used it for explicit calls to expound.alpha/expound
shouldn't it be injected only when using cider-jack-in-clojurescript
?
I just listed the command from the top of my head, don't know which one it is exactly 😛
0.17 predates the huge change of the connection api. i believe cljs migrated to clojurescript
@orestis i see it alters a var root. this may be similar to the map printing argument *print-namespace-maps*
not being honored. I think these bindings are per thread and nrepl uses 4 threads from a thread pool (i think). I think there is currently a bug in the way some of these bindings are propagated
anyone run into this issue? the new feature eval toplevel in comment breaks the auto completion in comment.
@doglooksgood i can get autocomplete here. are you unable to do this?
immediate workaround: (setq cider-eval-toplevel-inside-comment-form nil)
. I put this behind a flag to disable it if it ever caused problems
@doglooksgood if you want to file an issue you can include this workaround on the issue so if people google for it
I have that set to true. I see the bug with it true and don't see the bug with it set to nil. I put that enabling flag precisely because it's so important
> shouldn’t it be injected only when using cider-jack-in-clojurescript
? (edited)
Yes.
@dominicm No. We just decided to add a shorter alias to the original name. In general we’ll favour cljs
over clojurescript
in command names for the sake of brevity.