This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-02
Channels
- # arachne (1)
- # bangalore-clj (3)
- # beginners (4)
- # boot (6)
- # cider (3)
- # cljs-dev (14)
- # cljsrn (2)
- # clojure (309)
- # clojure-ireland (1)
- # clojure-russia (7)
- # clojure-spec (10)
- # clojure-uk (5)
- # clojureremote (2)
- # clojurescript (68)
- # cursive (7)
- # emacs (7)
- # luminus (3)
- # lumo (21)
- # off-topic (14)
- # om (1)
- # onyx (53)
- # perun (3)
- # re-frame (4)
- # slack-help (14)
- # unrepl (56)
- # untangled (3)
Installing unravel is now as easy as
sudo npm install -g lumo-cljs unravel-repl
and unravel localhost 50505
that involved doing a bunch of CLJ and little CLJS, what I really miss the most is this kind of stuff
no idea how that would work in a terminal but I got so used to having this it really felt bad working without it
so the elision system has me the most excited at the moment, normal print is so terrible in comparison 😛
ie. you use tools.logging
as normal but attach a special custom appender in development
Released version 0.1.3 with persistent readline history
@thheller you mean the ability to collapse/expand nested data structures interactively?
there are two challenges there
1. the elision system
2. presentation
for 1, what is already there is pretty good. We need to restrict print-length and print-depth
allowing you to request more data (continuation)
how do you mean?
for 2, I agree that squeezing this interactivity into an xterm is not ideal
you can do a lot (ascii tables etc.)
as I said above, something like tools.logging
. the issue I have with elision only on REPL print
but a browser in undoubtedly better suited for interactive printing
basically you want to use (log/warn "Got request" (eliding-pr-str request))
?
btw I've encountered the logging problem in the past as well
its everything I encounter I feel, messed with a bunch of shadow-build
the past few days and that has to work with the entire CLJS env
I worked on a react-native project where the entire app state was in an atom
printing that on every swap! is very useful for debugging
but it gets unwieldy quickly
so I built a half-baked eliding-prn that just cut off after n keys
a general solution to that would be handy
yeah exactly. it really feels terrible in CLJ when you are used to CLJS and the console
but its still in the browser, if we could move that to something like cursive that would be killer
well I did have the idea of hooking up unravel
to the browser
basically start a tiny web server and launch a chrome web browser on localhost:12345