Fork me on GitHub
#calva
<
2019-06-29
>
dominicm08:06:50

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.

cheatex09:06:39

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?

pez10:06:09

Hmmm, If you put just one color in there, maybe?

pez10:06:19

Also, that issue should be reported, I think. Doesn’t make sense to me that bracket highlight should be disabled.

pez10:06:15

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.

cheatex10:06:19

@pez single color works, takes time to align with the color theme thought

cheatex10:06:09

@pez should i fire the bug in calva or in https://github.com/tonsky/clojure-warrior ?

pez11:06:45

The Clojure Warrior repo, me thinks.

slipset13:06:36

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?

pez13:06:45

Probably issue, but you can give some examples here first, and I can test in my side.

d4hines17:06:24

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?

pez17:06:20

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.

d4hines17:06:10

What about clearing the REPL window? Just to visually clear up the screen, is that thing?

pez18:06:00

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...

d4hines18:06:59

Confirmed! Ctrl+l works!

d4hines18:06:55

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.

pez19:06:14

There is not much of parinfer in Calva. And, not sure what your million spaces are supposed to achieve. 😎

d4hines19:06:53

I tried toggle modes to Paren, and this seems much more what I expected.

d4hines19:06:03

Is there a way to get (s/explain spec some-failing-value) t

d4hines19:06:07

to print in the REPL?

d4hines19:06:11

Or anywhere in VS Code?

d4hines19:06:53

I’ll just use explain-data

pez19:06:34

Evaluate it to the repl?

d4hines19:06:55

s/explain wasn’t printing to the repl, it was just evaluating to nil.

d4hines19:06:02

s/explain-str is working great.

d4hines19:06:26

prn does the same thign