This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-25
Channels
- # announcements (8)
- # babashka (58)
- # beginners (59)
- # biff (4)
- # calva (39)
- # cider (2)
- # clj-kondo (8)
- # clj-together (4)
- # cljdoc (5)
- # cljsrn (1)
- # clojure (60)
- # clojure-australia (2)
- # clojure-europe (16)
- # clojure-nl (1)
- # clojure-norway (3)
- # clojurescript (13)
- # conjure (10)
- # cursive (9)
- # datomic (5)
- # dev-tooling (1)
- # emacs (6)
- # events (1)
- # graalvm (38)
- # graphql (5)
- # joyride (1)
- # kaocha (3)
- # lsp (23)
- # malli (2)
- # mount (2)
- # off-topic (31)
- # other-languages (13)
- # pathom (3)
- # polylith (12)
- # portal (4)
- # practicalli (22)
- # re-frame (6)
- # reagent (3)
- # releases (3)
- # sql (4)
- # squint (3)
- # tools-build (10)
- # tools-deps (10)
- # xtdb (4)
Hello!
Is it possible to make Cursive always run tests via the REPL (cf. https://cursive-ide.com/userguide/testing.html) when I click the green arrow next to deftest
or the green double arrow next to ns ,,,-test
?
I know I can go via the "Tools" menu, but I got quite accustomed to clicking the green arrows. Firing up a whole test runner for my current project takes quite some time, so I would like to know a convenient way to run tests via the REPL in a similar manner.
There isn’t at the moment, no, but I get that people would like that option. I’ll think about ways to achieve that.
What I did was bind the run and re-run commands to ^Q and shift-^Q. Iteration heaven. I can even use ^Q when I have navigated to different source file and made a change. I almost never take the trouble to customize key bindings, but here I saw a bigggg win.
I created an issue for this, so the request can be found outside of Slack: https://github.com/cursive-ide/cursive/issues/2770
is there any way to suppress warnings output to the REPL from Clojure or Java code over which one hasn't got control ?
if it's Java code that uses java.util.logging
, I've used the following in the past to suppress messages:
(import '[java.util.logging Logger])
(.setLevel (Logger/getLogger "org.javacode.mylib.MyClass") java.util.logging.Level/SEVERE)
But this requires you to know the name of the class triggering the warnings, which isn't always obvious or easy to discover if it's somewhere down in your dependencies.sadly it's not
it's actually coming from C code fprintfing to stderr
(via JNA)