This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-20
Channels
- # announcements (3)
- # babashka (74)
- # beginners (45)
- # biff (3)
- # calva (10)
- # cherry (1)
- # clojure (7)
- # clojure-austin (4)
- # clojure-europe (50)
- # clojure-losangeles (1)
- # clojure-nl (1)
- # clojure-norway (22)
- # clojure-uk (3)
- # cursive (14)
- # data-science (2)
- # datomic (1)
- # emacs (3)
- # events (5)
- # fulcro (13)
- # holy-lambda (64)
- # hyperfiddle (67)
- # introduce-yourself (1)
- # lsp (5)
- # off-topic (1)
- # rdf (1)
- # re-frame (5)
- # reitit (4)
- # releases (3)
- # shadow-cljs (89)
- # spacemacs (4)
- # squint (5)
- # timbre (9)
- # tools-deps (2)
Hi Calva friends! I'm still loving Calva very much, but recently there has been something EXTREMELY annoying. I know that every love relationship has those things, but it would be great if this one could be fixed 🙂 It's about "eval on save". I always work with at least three panes in VSCode: on the left I have the Calva repl out, in the middle I tend to have the unit tests, and on the right the production code. Recently (maybe last release because of https://github.com/BetterThanTomorrow/calva/issues/2389?) there was a change that unsaved files all of a sudden automatically get opened at strange times. Important context: I have both "auto save" set to "on focus change", and also Calva's "run on save" enabled. So now I have (unsaved) changes in my test file, I go to the other pane to edit the production code, and all of a sudden my test code is also opened on the right. Or I have unsaved changes, I command-click a symbol to go to a definition, and boom I'm right back where I came from because the changes got saved, code eval'ed, and then the file displayed again. I hope my rambling is making sense. Can this be fixed?
Hopefully this PR fixes the issue: https://github.com/BetterThanTomorrow/calva/pull/2403

Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.413
• Fix: https://github.com/BetterThanTomorrow/calva/issues/2327
• Fix: https://github.com/BetterThanTomorrow/calva/issues/2402
Thanks @dustingetz and @stefan.van.den.oord for reporting! ❤️ 🙏
Haha, yeah, when a regression is quickly found and reported, it is easier to be quick about it, because the change is fresh in mind. And also @stefan.van.den.oord was quick to test that the PR fixed his issue. Sometimes fixes get hanging a while because we’re giving it some time to be tested by those who experience the issue. Unfortunately it is a bit uncommon that we actually get help with testing. Anyway, thanks for noticing! ❤️
And don't forget about you and your team having setup great CI so that I actually could immediately and very easily test the vsix @U0ETXRFEW!!

I am super happy with our CI! Really great that @U9A1RLFNV wasn’t happy enough with it. 😃