This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (1)
- # beginners (429)
- # calva (41)
- # cider (19)
- # cljdoc (10)
- # cljsrn (6)
- # clojure (116)
- # clojure-europe (15)
- # clojure-italy (25)
- # clojure-nl (5)
- # clojure-spec (19)
- # clojure-uk (52)
- # clojurescript (99)
- # clojurex (14)
- # cursive (47)
- # data-science (1)
- # datomic (5)
- # duct (1)
- # figwheel (13)
- # fulcro (58)
- # graalvm (93)
- # jobs (3)
- # joker (9)
- # luminus (4)
- # nrepl (21)
- # off-topic (41)
- # pathom (25)
- # re-frame (7)
- # reitit (8)
- # ring-swagger (13)
- # tools-deps (13)
For some reason, go-to definition stopped working since I upgraded to the new calva (it’s been a while since i last used it), I jacked-in, loaded the namespace as usual, but it does not work. Is there a place where I can find logs other than the
Calva says and the developer console? (those where mostly empty)
@andremidea, do you have any nrepl dependency stuff in your project file or profile? (It used to be how you connected Calva, but now it would interfere with jack-in.)
That is really good to know. The README should probably contain a message about checking this for people coming from old Calva.
I’ve got a strange problem with setting up Calva on a new computer. It’s an early 2015 MacBook running macOS Sierra. Structural editing is not working. Parinfer is not working. Tab key is not indenting.
@grounded_sage, can you check the development console and see if you have any messages there that can hint us about what is not happening?
Yes, those are from the Calva extension, but it is something everybody gets and should not disable things. I wonder what is going on… What version of VS Code is it?
Only that one. We are on holidays and I don’t have a laptop atm so decided to use partners. I think it was originally called a MacBook C. I have done a VScode install. Calva is the only extension added.
I will try deleting VScode and doing a fresh install in a few hours when I have the laptop again. Though I don’t think this is the problem. Does VScode hold any meta settings/config that lingers after deleting the app.
The biggest thing that jumped out to me at first when I installed was that I couldn’t tab in a clj/cljs file.
I will try both of those when at computer. Command pallete and VScode insiders.
You are not supposed to be able to tab in a clj file with Calva. What should happen is that the code in the ”current” form gets formatted.
I’m still very new to VScode. I saw that Calva has Parinfer. Does it still do the bracket inference based on indentation? I know that Parinfer has gone through some changes since I last used also.
I was also having issues doing slurp/barf commands. It wasn’t working then it worked then it stopped working. So I’m just a little confused about what behaviours I should have.
Calva has very limited Parinfer. So, no. But it has a command that can infer parens from indentation
ctrl+alt+p. However, the structure can't be too broken for that to work.
Ok cool. Well this has been enlightening. I might have just not known how to use my tools :p
That sounds like a glitch. I have had problems with the paredit commands getting disabled when going between the repl window and the editors, but I had hoped those were sorted out.
I don’t really think I need Parinfer. Paredit and an auto format seems like the best way to handle lisp syntax.
Yea video would probably help. I’ll have another look at the docs because it might have just been me glancing over it all to lightly.
Decided to try an OS update. Perhaps could have waited for your response @pez haha. So will be a little while until I can give some more info