This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-28
Channels
- # aatree (3)
- # alda (8)
- # avi (21)
- # beginners (37)
- # boot (193)
- # cbus (1)
- # cider (29)
- # cljs-dev (8)
- # cljsjs (3)
- # cljsrn (20)
- # clojure (76)
- # clojure-dev (13)
- # clojure-miami (20)
- # clojure-portugal (2)
- # clojure-russia (220)
- # clojure-sg (2)
- # clojurebridge (5)
- # clojurescript (94)
- # community-development (14)
- # conf-proposals (110)
- # core-async (12)
- # cursive (12)
- # datascript (6)
- # datomic (14)
- # dirac (72)
- # emacs (49)
- # hoplon (86)
- # jobs (33)
- # jobs-discuss (1)
- # ldnclj (6)
- # lein-figwheel (1)
- # off-topic (56)
- # om (139)
- # onyx (29)
- # pedestal (17)
- # proton (23)
- # re-frame (45)
- # reagent (35)
- # ring-swagger (4)
- # test-check (1)
- # testing (8)
- # yada (11)
Oh, okay. My README will be pretty trivial anyway.
@austincrft: looks good to me so far! Just the readme link fix and I’ll merge it
@dvcrn: I used atom the whole day yesterday, didn't bother setting up REPL yet but it's working ok-ish in general
it's a bit laggy occasionally, is that similar for you?
the only problem I have is on initial save. Some plugin blocks the save event and I couldn’t find out which one yet
not really. I got the impression that it's more "constantly than that"
I'll try seeing if I can come up with a better description
def. appreciate all your work on this 👍 more beginner friendly editing environments matter!
getting this when trying to start a proto-repl: Error starting repl: Error: spawn lein ENOENT
looks familiar to anyone maybe?
the directory it's starting in seems fine
That's an error in the proto-repl
package
I found that but I'm on mac and I think the fix has already been released as well?
I think it has to do with Windows using different brackets
Oh, if you're on Mac I have no idea.
found it. I had lein installed via Nix which required special modification of $PATH and I guess node doesn't pick this up properly (not sure about that) — in any case specifying the path the the lein executable manually worked
@martinklepsch did you launch atom from terminal?
@dvcrn: Oh yeah, I fixed the links in the README.