This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-14
Channels
- # asami (1)
- # babashka (50)
- # beginners (70)
- # bristol-clojurians (6)
- # calva (36)
- # chlorine-clover (1)
- # cider (4)
- # clj-kondo (3)
- # cljdoc (49)
- # cljsrn (5)
- # clojure (96)
- # clojure-australia (3)
- # clojure-dev (1)
- # clojure-europe (84)
- # clojure-nl (4)
- # clojure-spec (9)
- # clojure-uk (65)
- # clojurescript (31)
- # community-development (6)
- # conjure (17)
- # cursive (8)
- # datascript (5)
- # datomic (12)
- # duct (3)
- # emacs (18)
- # figwheel-main (2)
- # fulcro (7)
- # helix (1)
- # jobs (3)
- # luminus (7)
- # off-topic (77)
- # pathom (3)
- # portal (1)
- # rdf (4)
- # re-frame (1)
- # reitit (4)
- # remote-jobs (4)
- # reveal (15)
- # rum (1)
- # sci (38)
- # shadow-cljs (22)
- # spacemacs (1)
- # specter (6)
- # sql (1)
- # test-check (1)
- # tools-deps (60)
- # vim (12)
Hey! I haven’t tried Calva for some time and I’ve been surprised - REPL window seems “weird”.
@pez Just to be clear - I am not trying to complain about work-in-progress things! I really appreciate all the time and effort you put in Calva. I just remember things differently and I want to make sure I don’t have something broken in my setup. 🙂
The file urls in that stack trace thing should be clickable. If they are not, then something is wrong. But in any case we are working with printing the stack traces in a more compact and usable way.
It would be nice if the …
were clickable, but they are just literal dots printed by the pretty printer. Fiddle with the pretty print settings to either disable or change the truncation limits. Or disable pretty printing, it can be toggled on/off without visiting settings.
Also, if you missed this PM, it could be worth a read: https://clojureverse.org/t/calva-summer-of-bugs-2020/6303
The newline after the prompts are intended. It makes for more horizontal space for editing forms there.
Hi. I haven't updated for a while and after installing the latest version all my paredit hotkeys went dead. If it try to perform some op via action panel a popup says something like "command 'paredit.deleteForward' not found".
Sounds like Calva fails to activate. Can you check the dev console log for hints on what goes wrong?
I see linter failure
Oct 14, 2020 10:14:19 PM org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint notify
INFO: Unsupported notification method: $/setTraceNotification
[Error - 10:14:22 PM] java.lang.IndexOutOfBoundsException
  at clojure.lang.PersistentVector.arrayFor(PersistentVector.java:158)
  at clojure.lang.PersistentVector.nth(PersistentVector.java:162)
Also
[2020-10-14 22:21:10.784] [exthost] [info] extension host started
[2020-10-14 22:21:10.802] [exthost] [info] ExtensionService#_doActivateExtension betterthantomorrow.calva {"startup":false,"activationEvent":"onLanguage:clojure"}
[2020-10-14 22:21:10.802] [exthost] [info] ExtensionService#loadCommonJSModule /home/zan/.vscode/extensions/betterthantomorrow.calva-2.0.126/out/extension
[2020-10-14 22:21:11.049] [exthost] [info] ExtensionService#_doActivateExtension borkdude.clj-kondo {"startup":false,"activationEvent":"onLanguage:clojure"}
Looks like both Calva and clj-kondo fails to start. Can you try uninstalling Calva and install only clj-kondo and see if you have linting?
I always have linting no matter if calva installed or not. After little experimenting I see that the error above is thrown every time code has unbalanced parens.
That linting error could be the same as this issue: https://github.com/borkdude/clj-kondo.lsp/issues/11
Which borkdude says probably happens here: https://github.com/borkdude/clj-kondo.lsp/blob/b72767efa23dda9f522edab9ec0f38f9afc61987/server/src/clj_kondo/lsp_server/impl/server.clj#L75
I can't install earlier version.Are you using the cog menu on the Calva extension in the Extensions side pane, then -> "Install another version"? That should show you older versions and you can click them to install. If that's not working, something is wrong with your installation, likely.