This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-01-23
Channels
- # announcements (1)
- # babashka (13)
- # cherry (12)
- # cider (6)
- # clj-kondo (3)
- # cljs-dev (28)
- # clojure (77)
- # clojure-europe (25)
- # clojure-nl (1)
- # clojure-norway (35)
- # clojure-uk (5)
- # clojurescript (31)
- # conjure (7)
- # cursive (12)
- # data-science (9)
- # datalevin (5)
- # datomic (8)
- # hyperfiddle (21)
- # jobs (7)
- # kaocha (19)
- # malli (26)
- # matrix (3)
- # releases (1)
- # shadow-cljs (42)
- # squint (95)
- # testing (2)
- # vim (14)
- # wasm (1)
Hello! Is there a way to have the output that is printed in the repl be wrapped when it exceeds buffer width? I searched through the docs but there was no mention of this, best I found was limiting the history Any ideas? I left here cider (emacs) vs cursive (intellij)
repl output already goes through pprint by default You can customize: https://github.com/clojure-emacs/cider/blob/60c9cea54315b08fb129cb57db5ade70ae28371a/cider-client.el#L315-L322
I'm trying to keep Cider REPL process alive while switching from a project to a library it uses to make some changes there, but face some problems when running tests in library file (deftests written in same file as code).
I find that cider-test-run-loaded-tests
loses track of what tests are loaded for library file after I switch REPL namespace from project ns to a library ns with cider-repl-set-ns
and load the library file including it's deftests with cider-load-buffer
.
After that running cider-test-run-loaded-tests
gives "No assertions (or no tests) were run. Did you forget to use βisβ in your tests?", while I can still run specific deftests in the library file at point with cider-test-run-test
or use (run-tests *ns*)
.
Everything works as expected after restarting Cider from the library ns and loading buffer again.
Hmmm, isn't this just that cider-test-run-loaded-tests
looks for tests in the current project?
We don't scan all the namespaces in the classpath for files with :test metadata - would be bit of an anti-feature (as more often than not, would run undesired tests)
Edit: I'm wrong, there's cider-test-run-loaded-tests
and cider-test-run-project-tests
. Issue welcome
Alright, copied here https://github.com/clojure-emacs/cider/issues/3611