This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-01
Channels
- # announcements (2)
- # babashka (10)
- # beginners (133)
- # calva (28)
- # cestmeetup (1)
- # chlorine-clover (31)
- # cider (21)
- # clj-kondo (29)
- # cljs-dev (252)
- # clojure (60)
- # clojure-europe (24)
- # clojure-nl (3)
- # clojure-spec (13)
- # clojure-uk (17)
- # clojurescript (47)
- # conjure (20)
- # datascript (2)
- # datomic (4)
- # figwheel-main (4)
- # fulcro (71)
- # helix (16)
- # jobs (1)
- # meander (56)
- # mount (1)
- # off-topic (15)
- # pathom (25)
- # re-frame (17)
- # reagent (5)
- # remote-jobs (1)
- # shadow-cljs (92)
- # sql (10)
- # tools-deps (71)
- # xtdb (14)
@mauricio.szabo Thanks for heeding my advice on the instructions for Chlorine setup, that should help anyone else like me to get started 🙂
Great! If you have any other question, or documentation problems, please open another issue in GitHub :)
Hello all, after updating to 0.7.3
I observe sometimes Atom closing itself after evaluation some functions. Anyone had the same issue?
Nope. ClojureScript or Clojure? How is your REPL started?
Clojure, I started with this clj -J'-Dclojure.server.repl={:port,5555,:accept,clojure.core.server/repl}'
Hmm, that's pretty much how I start my REPL every time and I've never seen Atom close/quit/crash when evaluating a function. Is it a particular function evaluation causing this? i.e., can you repro reliably?
@fabrao What O/S are you running Atom on?
And if you downgrade to 0.7.2, the problem goes away?
I´m never downgrade in versoins 🙂 , the thing is that when open Atom again it restore the same state as before hanging
@fabrao try to downgrade, with apm install [email protected]
, and see if the problem goes away
(since you're on Windows, you'll need to open a terminal window and probably navigate to wherever Atom puts the apm
binary in order to run that)
Yes, I always forget that Windows don't set PATH for most of things 😞
I'm not at my Windows machine right now so I can't tell you where to look, sorry.
@fabrao do you use simple refresh, or full? (or both are failing?)
I'll look at this issue, too.
@mauricio.szabo I´m not tried simple, only full.
Okay. I'll look at it. (BTW, I'm thinking about removing refresh - it's easily replicated by the .cljs file, and more configurable too. I'll check if there's a way to keep an "official, over-writable version")
@fabrao ok, found the bug. Will publish a fix
For refresh. There is indeeed a bug 😞
Just published a fix for refresh (full and simple) on version 0.7.4 🙂
Yes, I also develop Chlorine in Chlorine with shadow-cljs 😄
What were the steps you tried? Did you start shadow-cljs, started a build, connected Chlorine to the socket repl, then ran the "connect embedded" command?