This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-13
Channels
- # aleph (1)
- # beginners (105)
- # boot (6)
- # cider (9)
- # cljs-dev (61)
- # cljsrn (59)
- # clojure (132)
- # clojure-germany (1)
- # clojure-italy (6)
- # clojure-russia (18)
- # clojure-spec (1)
- # clojure-uk (58)
- # clojurescript (56)
- # core-async (1)
- # cursive (17)
- # datomic (20)
- # docs (1)
- # duct (5)
- # editors (1)
- # emacs (7)
- # events (2)
- # figwheel (7)
- # fulcro (30)
- # graphql (8)
- # jobs (3)
- # leiningen (23)
- # luminus (14)
- # mount (6)
- # off-topic (41)
- # onyx (14)
- # protorepl (2)
- # re-frame (7)
- # reagent (32)
- # shadow-cljs (236)
- # tools-deps (92)
- # unrepl (8)
- # vim (60)
- # yada (1)
Btw, I’ve added a couple of small things to address running custom cljs repls:
* there’s now a custom type that will just prompt you for the form to invoke to start the repl
* there’s now a function (`cider-register-cljs-repl-type`) that you can use in your init.el
(or whatever) to add new repl types permanently.
so i'm finding that when i attach CIDER to a repl running in a terminal with cider-connect
that my timbre logging stops being printed on the terminal and starts being appended to the emacs repl buffer
has anyone figured out how to stop this happening - i'd like it to carry on being printed to the terminal but not the emacs repl buffer
Yeah, that’s a known problem that’s easy to fix, but for some reason we haven’t fixed yet.
Basically this patch has to be finished. In its current form it will solve your problem, but I want to make this behaviour something that can be dynamically controlled from CIDER, as opposed to hardcoded.
np - it's been bugging me for ages and i only just got to querying what's going on after i killed emacs... waiting a while longer for a solution won't do me any harm 🙂