This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-22
Channels
- # ai (1)
- # announcements (4)
- # babashka (23)
- # beginners (27)
- # biff (17)
- # calva (5)
- # clerk (6)
- # clj-commons (27)
- # clj-kondo (35)
- # clojars (12)
- # clojure (27)
- # clojure-denver (3)
- # clojure-europe (71)
- # clojure-norway (7)
- # clojure-spec (5)
- # clojure-uk (2)
- # clojurescript (45)
- # data-science (9)
- # datomic (4)
- # dev-tooling (2)
- # devcards (1)
- # hoplon (2)
- # hyperfiddle (36)
- # introduce-yourself (3)
- # malli (11)
- # missionary (2)
- # off-topic (63)
- # polylith (5)
- # rdf (2)
- # reagent (12)
- # schema (1)
- # shadow-cljs (11)
- # sql (6)
- # tools-deps (23)
- # xtdb (6)
I'm helping a colleague get set up with Clerk but she is using VSCode and Calva and it's not working correctly ... she is changing files that are watched but the browser does not update and I don't see and logging in the REPL window. I know this works, it's my project that I normally operate in using Cursive; has anyone hit any issues when using Calva?
I also use Cursive so can't help on that front, but sometimes I have to manually clear Clerk's cache to get my changes. Doubt that's the issue, but since it's hit me a few times, I thought I'd mention it.
if they’re using the file watcher it should be editor independent. Maybe a second clerk issue is running? Do you see the log output?
Just got her set up on Cursive and she's seeing the same problem. She's going to reboot her machine, but it's likely that she's running two Clerks perhaps.
Just a minor thing; IntelliJ only saves to disk on-blur, that is, when you switch to a different application. At least it works that way on my machine. What this means is that when I change my frontend files, figwheel does not reload the code in the browser until I either manually save (Cmd + S) or switch focus to some other application (for example the browser).
Your problem sounds more involved, but you should take heed of the aspect I mention as well, if it's relevant for your setup, as I guess it'll muddle your perspective of your testing if you don't.