This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-03
Channels
- # announcements (55)
- # babashka (14)
- # beginners (49)
- # biff (9)
- # calva (73)
- # cider (14)
- # clerk (8)
- # clj-kondo (6)
- # clojure (92)
- # clojure-dev (4)
- # clojure-europe (18)
- # clojure-norway (62)
- # clojure-uk (5)
- # clojuredesign-podcast (4)
- # clojurescript (34)
- # cursive (40)
- # data-science (4)
- # datomic (5)
- # dev-tooling (1)
- # eastwood (6)
- # emacs (107)
- # figwheel-main (9)
- # fulcro (13)
- # gratitude (9)
- # hyperfiddle (5)
- # introduce-yourself (2)
- # off-topic (45)
- # overtone (23)
- # portal (5)
- # releases (3)
- # shadow-cljs (6)
- # specter (1)
- # squint (32)
- # timbre (4)
- # vscode (2)
what 'the' way to redirect prints and stuff to my repl from a thread? I expected (def something *out)
evaluated from the REPL then binding *out
from within the thread to work, but I guess the bound *out*
that I save is meant for a single nrepl message
I sense that
(binding [*out* (io/writer System/out)]
(println 42))
should do it, however currently it stack overflows 😱
Otherwise I hadn't hard of an "api" that we had for this.
You can however use any logging framework - its output should go to the replinfo
on timbre
doesn't go to the repl (as is at least). i jacked in remotely, and due to issues i dont have a way to read stdout/journal right now
> info
on timbre
doesn't go to the repl
IIRC it does for basic cases on local connections.
Using the repl as a stdout viewer for remote connections is kind of a fringe use case IMO, there are simpler tools e.g tail
/ less
over ssh.
We'd welcome a PR that made this easier (w/o losing simplicity), otherwise it seems an unlikely improvement
The mentioned Stackoverflow shouldn't really happen, maybe by fixing it we'd enable more usage patterns
yeah exactly 😛 I can't tail right now due to a bug, which I can fix but I took the opportunity to figure out what if I couldn't
> hm I'm not starting nrepl with the cider handler, maybe that's a cause
likely, cider-nrepl has a special out
middleware
stumbled on it's source and now here https://docs.cider.mx/cider-nrepl/nrepl-api/supplied_middleware.html
wrap-out
-
Yes
out-subscribe/out-unsubscribe
Echo the server's output stream to client sessions.