This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-27
Channels
- # bangalore-clj (1)
- # beginners (27)
- # boot (16)
- # cider (14)
- # cljs-dev (94)
- # cljsrn (8)
- # clojure (229)
- # clojure-dev (5)
- # clojure-dusseldorf (6)
- # clojure-italy (8)
- # clojure-norway (8)
- # clojure-russia (22)
- # clojure-sanfrancisco (2)
- # clojure-spec (48)
- # clojure-uk (44)
- # clojurescript (47)
- # core-async (87)
- # cursive (43)
- # datascript (22)
- # datomic (20)
- # defnpodcast (5)
- # emacs (6)
- # hoplon (4)
- # jobs-rus (4)
- # keechma (2)
- # klipse (8)
- # leiningen (2)
- # luminus (2)
- # lumo (14)
- # om (38)
- # onyx (4)
- # overtone (3)
- # pedestal (41)
- # planck (72)
- # powderkeg (42)
- # proton (46)
- # protorepl (9)
- # reagent (9)
- # ring (47)
- # ring-swagger (5)
- # rum (7)
- # sql (22)
- # unrepl (1)
- # untangled (24)
- # vim (19)
- # yada (5)
Does om next work with protorepl? I'm getting errors about resolving the defui macro.
Quick question from a terminal repl convert: When I start a proto-repl tab I see it reloading all the code in the namespace, but then when I try to run something like (require '[thingisaw.reloaded.core :as foo])
to do something I get a namespace not found error. I’m guessing my old cli workflow isn’t idiomatic for proto-repl but I’m not sure what is.
You'll need to turn off all the REPL refresh options in ProtoREPL's package settings for your workflow to continue.
ProtoREPL's "opinionated setup" guide assumes you have a fully "reloaded" workflow with Component etc.
Ah! Ok. Thank you. I should probably give the preferred workflow a try, but in the short term I’ll try turning off the refresh.
We’re still dealing with code that is not entirely managed by Component so we can’t use ProtoREPL in that “opinionated” setup.
Yup. I just turned off refresh and all is well. I think this might make me switch to Atom now.
I switched from Emacs to Atom after seeing Jason present ProtoREPL at Clojure/conj back in December.