This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-28
Channels
- # beginners (79)
- # boot (24)
- # cider (5)
- # clara (5)
- # cljs-experience (5)
- # clojure (126)
- # clojure-greece (5)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-russia (1)
- # clojure-spec (21)
- # clojure-uk (31)
- # clojurescript (151)
- # community-development (20)
- # cursive (25)
- # datomic (24)
- # flambo (1)
- # fulcro (312)
- # graphql (10)
- # hoplon (20)
- # juxt (2)
- # keechma (6)
- # leiningen (7)
- # luminus (4)
- # om (4)
- # onyx (7)
- # parinfer (24)
- # protorepl (1)
- # re-frame (7)
- # reagent (13)
- # shadow-cljs (19)
- # spacemacs (14)
- # specter (14)
- # uncomplicate (22)
- # unrepl (1)
@bpiel so I'm working with sayid in spacemacs again, and I would like to use it with a gui program I'm running. Unfortunately, this makes putting tests in a buffer to run with sayid unpractical. Is there anyway, currently, to get sayid to trace things run from a repl as well?
@donyorm Just woke up (Philly). What sort of things are you running from the repl? If you called a traced function from the repl, it should work as usual.
if there's an inner trace on a function that you call, the function's internals should get captured as usual
If I run into the issue again I'll let you know/try to collect enough data to report a bug
I'm using spacemacs in holy-mode and I hate evil-lisp-state. Is there a way to use paredit or something else instead?