This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-27
Channels
- # bangalore-clj (2)
- # beginners (37)
- # boot (16)
- # cider (17)
- # clara (4)
- # cljs-dev (351)
- # cljsrn (16)
- # clojure (219)
- # clojure-belgium (4)
- # clojure-dev (3)
- # clojure-france (2)
- # clojure-italy (24)
- # clojure-russia (23)
- # clojure-spec (55)
- # clojure-switzerland (3)
- # clojure-uk (89)
- # clojurescript (121)
- # cursive (2)
- # datomic (29)
- # devops (2)
- # graphql (8)
- # hoplon (15)
- # immutant (5)
- # lein-figwheel (4)
- # liberator (3)
- # luminus (18)
- # off-topic (9)
- # om (6)
- # onyx (31)
- # pedestal (48)
- # precept (9)
- # re-frame (19)
- # reagent (63)
- # ring-swagger (69)
- # robots (1)
- # slack-help (14)
- # spacemacs (12)
- # sql (2)
- # test-check (4)
- # unrepl (28)
- # untangled (5)
- # yada (3)
Tangentially related to unrepl but this could benefit from machine printing and elision:
yeah, anything tree like really
but tracing is a great example of that
I wonder if it works in cljs as well
This is what i have found: https://nodejs.org/dist/latest-v8.x/docs/api/tracing.html
That JVM tracer is cool, how do you hook it up?
I guess it is in clojure.tools.trace
?
In my case the JVM has to be started with -Xdebug -agentlib:jdwp=transport=dt_socket,server=y,suspend=n
(no explicit port required)
Well that is great, node has a debugging/inspecting layer, not an expert however and it looks very limited: https://nodejs.org/dist/latest-v8.x/docs/api/debugger.html
@cgrand debugging/tracing/repl-driven development could be a killer feature of nrepl
@richiardiandrea you can attach chrome to a running nodejs instance for a full blown debugger
Yeah I have recently enabled boot to work with Dirac for a Repl in there for my colleagues 😀
But it is not the same thing 😀
And I don't personally use it, at some point I will help porting unrepl to cljs just don't have enough time now and when I have time, it is too little and I prefer to tackle smaller problems
re: cljs port, dynamic ns are not seen by require (self-hosted) so: • either add workarounds in the blob • fix cljs. What’s the best course of procrastination? 🎵
@cgrand I guess you spoke with D. Nolen already? What did he say? Usually patches to self host are more likely to happen, especially because you have very active projects/maintainers behind it
@richiardiandrea I forgot you opened the issue for that
the fix should cover both slef-host and regular 😕 to not create yet another divergence
Ok yeah that is tougher then, Darwin already proposed something and got bounced 😀
(don't remember the details now)
🎶 procrastination isn't good for me 🎶