This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-29
Channels
- # announcements (1)
- # beginners (40)
- # calva (30)
- # cider (3)
- # clj-kondo (1)
- # cljdoc (12)
- # clojure (79)
- # clojure-dev (7)
- # clojure-france (4)
- # clojure-spec (10)
- # clojure-uk (13)
- # clojurescript (19)
- # core-async (1)
- # core-typed (1)
- # cursive (2)
- # datomic (2)
- # emacs (3)
- # events (1)
- # kaocha (2)
- # klipse (14)
- # off-topic (26)
- # pathom (1)
- # reagent (8)
- # rewrite-clj (8)
- # shadow-cljs (22)
- # tools-deps (18)
I completed the integration of Calva into Edge. If you'd like to see how it looks, clone Edge and try jacking into the example project vent in examples/tutorial.vent. You will need to use the aliases :dev
, :build
, :dev/build
.

Hi. When I set "clojureWarrior.bracketColors"
to []
matched bracket highlight also gets disabled. Is it an intended behavior? Can I have match highlight without that colorly thing?
Also, that issue should be reported, I think. Doesn’t make sense to me that bracket highlight should be disabled.
btw, I can recommend using a grey scale rainbow, if you think the colors are too much, but still think that some indentation information would be nice.
@pez should i fire the bug in calva or in https://github.com/tonsky/clojure-warrior ?
It seems to me that the various paredit cut commands do not stick things in the cut-buffer. Is it only me, is it intentional, or should I file an issue?
So, thanks to your hints, @pez, I’ve got intellisense working (by opening a browser on the host machine). In Spacemacs, as I typed a function call, I would get hints about the arity (i.e the names of the parameters). Is there a way to see that in Calva?

There is no good way to see it as you type and need it, unfortunately. But there is a mounting pressure to add such a way. Chip on on the issue on GitHub.
What about clearing the REPL window? Just to visually clear up the screen, is that thing?
I might have dreamed it, but I think I might have added that... Try ctrl+l
. If it does not do it, then maybe I ran into problems implementing it...
Confirmed! Ctrl+l works!
You da man! One last question (I shouldn’t say that :P): am I using parinfer wrong? To add the next line, I end up having to press spacebar a million times. That seems to defeat the purpose a bit.
There is not much of parinfer in Calva. And, not sure what your million spaces are supposed to achieve. 😎
I tried toggle modes to Paren, and this seems much more what I expected.
Thanks!
Is there a way to get (s/explain spec some-failing-value)
t
to print in the REPL?
Or anywhere in VS Code?
I’ll just use explain-data
s/explain
wasn’t printing to the repl, it was just evaluating to nil
.
s/explain-str
is working great.
prn
does the same thign