This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-01
Channels
- # atom-editor (11)
- # babashka (25)
- # beginners (142)
- # boot (9)
- # calva (3)
- # cider (19)
- # clara (15)
- # clj-kondo (6)
- # cljs-dev (20)
- # clojars (11)
- # clojure (164)
- # clojure-dev (9)
- # clojure-europe (6)
- # clojure-italy (17)
- # clojure-nl (3)
- # clojure-spec (19)
- # clojure-sweden (10)
- # clojure-uk (23)
- # clojurescript (34)
- # code-reviews (31)
- # conjure (20)
- # cursive (14)
- # datomic (54)
- # emacs (1)
- # fulcro (51)
- # graalvm (24)
- # graphql (6)
- # helix (3)
- # jobs (3)
- # kaocha (1)
- # malli (2)
- # meander (15)
- # off-topic (81)
- # pathom (2)
- # re-frame (43)
- # reagent (26)
- # reitit (1)
- # releases (1)
- # sci (12)
- # shadow-cljs (29)
- # sql (22)
- # timbre (3)
- # tools-deps (15)
What is the use of the cider-nrepl middleware? Do I really need it to connect to an nrepl server using cider?
What will I miss if I don’t use the middleware, I am able to connect fine to an nrepl server without the middleware
I have inherited a project where there is hard dependency on cider-nrepl. We are not trying to aot compile our project for distribution so that the source is unavailable. I not be including project.clj in my jar file but cider-nrepl needs the project.clj and hence stops the jar from running because of this.
Okay I got this https://docs.cider.mx/cider-nrepl/nrepl-api/supplied_middleware.html. Nevermind
@frozenfire1992 CIDER will work even without cider-nrepl, but it will be limited when it comes to functionality.
Thank you! 🙂
I think that making a hard dep to some project is kind of weird, as I doubt anyone would be running any of the advanced debugging features in production, but who knows.
Can I somehow "open" the repl buffer literally? SImilar to what emacs/spacemacs offer me by default when opening a large file? The thing is that Emacs gets really slow when my app logs lot of messages to standard out so I'd like speed it up
@jumar I guess you can just enable saving the REPL log to a file and open that file.
It's rather special, but in this case I was also debugging an issue when the error happened only when writing to stdout
I guess then you can save your REPL buffer as a file and work with that file directly.
My problem is that Emacs/Cider is just really slow in this case - in terminal it’s fine but Emacs will freeze for up to a minute while waiting for the output to be written to the repl buffer; the process that generates this output only takes several seconds
Asked in #spacemacs too: https://clojurians.slack.com/archives/C09C8GRLY/p1593670518006700
Emacs has well known issues with handling of long lines. That’s nothing that can be fixed in CIDER and the best recipe is to keep the REPL buffer’s size in check. https://docs.cider.mx/cider/repl/configuration.html#auto-trimming-the-repl-buffer
I know it might not help in your case. I disable logging to console, enable logging to a file and have a separate terimal window open with tail -f log.
@U15BH4U4V that could work in most of the cases; I'll give it a try