This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-05
Channels
- # announcements (17)
- # architecture (5)
- # babashka (12)
- # beginners (155)
- # calva (18)
- # chlorine-clover (2)
- # cider (57)
- # circleci (2)
- # clojure (151)
- # clojure-europe (4)
- # clojure-gamedev (20)
- # clojure-italy (18)
- # clojure-nl (4)
- # clojure-norway (3)
- # clojure-spec (8)
- # clojure-uk (95)
- # clojurescript (70)
- # core-async (68)
- # css (3)
- # data-science (13)
- # datascript (1)
- # datomic (16)
- # docker (2)
- # figwheel-main (41)
- # fulcro (34)
- # graalvm (6)
- # graphql (7)
- # jobs (14)
- # joker (2)
- # kaocha (1)
- # leiningen (2)
- # malli (3)
- # midje (2)
- # overtone (1)
- # reagent (8)
- # reitit (6)
- # ring-swagger (1)
- # schema (2)
- # shadow-cljs (6)
- # spacemacs (3)
- # specter (5)
- # timbre (3)
- # uncomplicate (1)
@pez Peter, I’m using Calva for several weeks and I love how well integrated it is with shadow-cljs. Thank you for all the hard work!
I have a question about “Run custom REPL Command”. Is it possible to run a REPL command in the current namespace? If I leave ns
parameter empty, it seems to jump to the user
namespace
No, but that is an excellent suggestion. I think it makes sense to have that behaviour for when you do not enter a namespace, since you can always specify user
. Please file as a feature request on the repo.
I haven’t had any issues for a while. I started monitoring the processes with top. There is CPU spikes on jack in and namespace loading. And I wait for spikes to come down before performing the next operation.
It’s likely that there was some runaway CPU work happening as I would eagerly perform operations such as namespace loading and sending code the the repl as soon as it returns (the CPU still under heavy load at this point). Then it would lock up/spin out of control and never come down.