Fork me on GitHub
#calva
<
2019-06-28
>
pez07:06:53

Dear Calva-friends, the Legacy Calva extensions are causeing major confusion for people who looke for Clojure extensions for Code. I need to come up with a plan for how to kill those old extensions. Starting with an inventory. Anyone of you still using Calva Legacy? If so, why?

slipset07:06:31

Just dropped in btw to say that I got a co-worker up and running on Calva, and he’s super stoked 🙂

pez07:06:40

I don't know if you can edit your reviews on the vs code marketplace, but if you can, that would go very well there! https://marketplace.visualstudio.com/items?itemName=betterthantomorrow.calva&amp;ssr=false#review-details

pez08:06:28

Yeah. We have solved it for the repl window, if I understand your suggestion correctly. Should be a piece of cake. Famous last words.

slipset08:06:30

You “solved” it 🙂

slipset08:06:18

The thing showing the args disappears at the moment your cursor leaves the fn-name.

pez08:06:57

Yeah, that might be tricky to fix. But haven't looked at it so maybe it's not that hard. In any case, you'll have to describe the feature you want like I'm an idiot. 😎 Please update that issue with everything you think I need to solve it properly.

d4hines12:06:17

So, since upgrading to v2, I haven’t been able to get docstrings on hover. Any ideas?

pez13:06:32

That probably means you do not have the dependencies injected correctly in the REPL server. I guess you still can't jack-in so for connecting you need to: 1. Make sure shadow-cljs.edn is clean from cider, piggieback, anything like that. 2. Start the REPL using shadow-cljs -d cider/cider-nrepl:0.21.1 watch :app

d4hines13:06:10

Thanks, I’ll give that another try when i have a chance (`-d` somehow caused things not to work any more…, but I’ll fiddle with it more later)

d4hines13:06:15

Thanks, I’ll give that another try when i have a chance (`-d` somehow caused things not to work any more…, but I’ll fiddle with it more later)

pez13:06:28

It could also be that v2 is not as friendly for setups involving VMs and stuff...

grounded_sage15:06:48

I don’t know why I am having so much troubles getting Calva working on this computer :(

pez15:06:50

How is it not working?

grounded_sage16:06:03

I’ve done a clean install of VScode. It does keep settings around after deletion on Mac. So I removed those as well.

grounded_sage16:06:25

I can’t seem to get any structural editing working. I can’t get it to jack in. Both worked for a brief moment. At independent times. From my perspective I’ve done nothing different for these different behaviours.

grounded_sage16:06:02

It’s most likely a user error but I am completely stumped and scratching my head

linkerfelix16:06:47

Hey pez, I think I have to annoy you again. Sometimes, I have the feeling that calva ends up in a bad state when annotating my files with issues. Certain issues don't go away when they should. The strange thing is that everything works as expected in the REPL and compiling gives the correct output in "Calva says" but the linting simply doesn't go away. Confer this example:

linkerfelix16:06:40

However, the namespace is used:

linkerfelix16:06:09

And furthermore, the compiler is able to resolve the symbol and Calva says now says that everything is fine. I'm also able to load the namespace into my REPL.

linkerfelix16:06:50

Is there something wrong with my workflow? Is there any way to really reload the file? Because just executing again does not change the linting.

pez18:06:23

@linkerfelix , I don't know what's going on with the linter. But in Calva the linting is a totally separate process from the compiler. So reloading the file won't change anything with the linting report. What you could try is to disable the Calva linter and install the extension Clojure-lint, by @marc-omorain, instead. It uses clj-kondo instead of Joker, and should be quite competitive in features.

borkdude18:06:37

Parse error: Unable to resolve symbol doesn't come from clj-kondo, but from joker

borkdude18:06:55

(ok, that's what you were saying)

pez18:06:18

Yeah, I am not suggesting … yeah. you beat me to it. 😃