This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-19
Channels
- # aws (2)
- # beginners (135)
- # boot (20)
- # chestnut (7)
- # cider (18)
- # clara (5)
- # cljs-dev (50)
- # cljsrn (30)
- # clojure (252)
- # clojure-italy (9)
- # clojure-losangeles (5)
- # clojure-russia (8)
- # clojure-spec (33)
- # clojure-uk (5)
- # clojurescript (32)
- # clr (4)
- # cursive (5)
- # data-science (1)
- # datascript (1)
- # datomic (40)
- # emacs (1)
- # fulcro (18)
- # graphql (11)
- # hoplon (3)
- # lein-figwheel (2)
- # lumo (47)
- # off-topic (2)
- # om-next (3)
- # onyx (10)
- # pedestal (22)
- # protorepl (6)
- # re-frame (7)
- # reagent (38)
- # ring (1)
- # ring-swagger (5)
- # rum (3)
- # spacemacs (19)
- # specter (5)
- # vim (13)
- # yada (16)
If I use Chestnut's take on starting up Figwheel (using danielsz/system and (user/go)
then it seems like Vim can't see that Figwheel is started.
result:
Figwheel System not initialized.
Please start it with figwheel-sidecar.repl-api/start-figwheel!
java.lang.NullPointerException:
does anyone know how to make (go)
work here? I just work around it for now with the usual (start-figwheel!)
in the REPL and this seems to work OK at the cost of not being able to really use the whole (reset)
thing for the CLJ side of life
@rgm try Piggieback (figwheel-sidecar.system/repl-env (:figwheel-system reloaded.repl/system) nil)