This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-21
Channels
- # arachne (1)
- # aws-lambda (50)
- # beginners (10)
- # boot (59)
- # capetown (4)
- # cider (9)
- # cljsjs (27)
- # clojure (249)
- # clojure-berlin (8)
- # clojure-finland (7)
- # clojure-germany (1)
- # clojure-italy (6)
- # clojure-nl (7)
- # clojure-russia (91)
- # clojure-spec (100)
- # clojure-uk (61)
- # clojureremote (2)
- # clojurescript (171)
- # core-async (11)
- # cursive (31)
- # data-science (1)
- # datascript (2)
- # datomic (11)
- # dirac (2)
- # emacs (16)
- # events (1)
- # hoplon (142)
- # juxt (4)
- # lein-figwheel (9)
- # leiningen (10)
- # luminus (7)
- # lumo (44)
- # mount (3)
- # off-topic (150)
- # om (18)
- # onyx (5)
- # perun (12)
- # planck (12)
- # protorepl (13)
- # re-frame (28)
- # reagent (8)
- # ring (1)
- # ring-swagger (10)
- # spacemacs (2)
- # specter (11)
- # sql (14)
- # untangled (99)
- # vim (18)
- # yada (2)
Hi all. I’ve just discovered protorepl. I have it installed and for the most part it’s working well; I can evaluate general expressions and the real-time evaluation in my source files works. However, when I try to evaluate expressions (in the protorepl tab) which reference definitions in my source file, it can’t find them.
@tarmes, I had not noticed the :reloading...
, but that's the same behavior that I've been working with as well, that is, I need to load the context into the repl manually.
with proto-repl:execute-selected-text
aka cmd-s
but I should add, that I'm only a week into this myself ;^)
@tarmes most of the time I work by evaluating blocks of code in a scratch file or namespace and sending to the REPL. I would recommend working that way for the best experience if working with code defined in a namespace.