This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-10
Channels
- # beginners (15)
- # boot (15)
- # cider (6)
- # cljs-dev (231)
- # cljsjs (1)
- # cljsrn (26)
- # clojure (147)
- # clojure-argentina (1)
- # clojure-dev (8)
- # clojure-germany (1)
- # clojure-italy (26)
- # clojure-russia (2)
- # clojure-spec (83)
- # clojure-uk (154)
- # clojurescript (123)
- # conf-proposals (3)
- # core-async (5)
- # cursive (26)
- # datascript (21)
- # datomic (120)
- # emacs (2)
- # graphql (9)
- # hoplon (195)
- # instaparse (16)
- # jobs-discuss (1)
- # leiningen (8)
- # luminus (8)
- # lumo (7)
- # off-topic (17)
- # om (7)
- # om-next (3)
- # parinfer (121)
- # pedestal (5)
- # planck (13)
- # re-frame (11)
- # reagent (21)
- # ring-swagger (2)
- # spacemacs (28)
- # uncomplicate (3)
- # unrepl (7)
- # untangled (34)
- # vim (5)
Hey folks, how do you debug Clojure(Script) in NeoVim? Does anyone use something smart like a debugger? My current workflow is mostly evaluating forms and adding log statements in the function I am debugging and looking at the stacktrace. Sometimes I even go back to Spaccemacs just for the debugger
Advice from stu: http://blog.cognitect.com/blog/2017/6/5/repl-debugging-no-stacktrace-required
I've been thinking about neovim-client and component... Would it make sense to make it component friendly/based? I mean plugins can make use of other components and even substitute the rpc/msgpack implementation if desired.. That way we can get rid of the future/try/loop/when-let chain...