This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-08
Channels
- # announcements (6)
- # beginners (100)
- # calva (17)
- # cljs-dev (31)
- # cljsrn (2)
- # clojars (3)
- # clojure (137)
- # clojure-australia (1)
- # clojure-europe (41)
- # clojure-gamedev (3)
- # clojure-italy (1)
- # clojure-nl (3)
- # clojure-poland (16)
- # clojure-serbia (7)
- # clojure-taiwan (1)
- # clojure-uk (10)
- # clojurescript (10)
- # cursive (25)
- # data-oriented-programming (4)
- # datomic (26)
- # fulcro (39)
- # graalvm (6)
- # jobs (2)
- # jobs-discuss (2)
- # kaocha (19)
- # klipse (1)
- # leiningen (3)
- # lsp (18)
- # malli (21)
- # meander (26)
- # off-topic (29)
- # pathom (39)
- # polylith (3)
- # practicalli (2)
- # re-frame (11)
- # reitit (8)
- # rewrite-clj (7)
- # sci (11)
- # shadow-cljs (44)
- # sql (8)
- # tools-deps (32)
- # xtdb (3)
If anyone else is having issues with the debugger with VS Code 1.54 please chime in on this issue with details like OS and project type: https://github.com/BetterThanTomorrow/calva/issues/1055. I cannot reproduce the issues on Manjaro Linux or Windows 10 Pro.
Hi all, any ideas on how to get calva to auto generate the correct namespace? I am using the re-frame template out of the box and I only get the namespace of new files to be the name of the file. I went through the readme and I can’t see what I am missing.
With auto-generate namespace you mean when you crate a new file and the namespace added to that file?
@U0ETXRFEW yes exactly
I’m jacked in, and I have the correct source-path as generated in the re-frame template. I’ve tried also adding source-path to a few other places in the config map, but nothing has worked so far
@U9A1RLFNV we should let lsp do this, right?
@U0ETXRFEW I think that would be best going forward
Need help testing a VSIX again, dear Calva friends. I’ve added a command for evaluating the code from start of the list up to the cursor. Sounds simple enough, which it is. But I had to restructure the select-for-evaluation code a bit because gnomes and kittens where in the line of fire. So now I could have broken something. My testing indicates I haven’t, but it is late here in the North… • Here’s the PR with some details: https://github.com/BetterThanTomorrow/calva/pull/1061 • Here’s the VSIX: https://11931-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.178-1057-evaluate-to-point-b54846a6.vsix
@U0ETXRFEW - have used on and off for a few hours today sans issues. The new eval-to-cursor facility (nice!) doesn't so far seem to have broken anything for me.
It really is a nice facility. I've been wanting to add it for quite a while, but procrastinated the needed restructuring. Thanks for giving it a spin!
Is this feature auto-updated with VS Code or do I have to manually update it?