This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-19
Channels
- # 100-days-of-code (12)
- # beginners (116)
- # calva (2)
- # cider (16)
- # cljdoc (5)
- # cljs-dev (26)
- # clojure (161)
- # clojure-italy (7)
- # clojure-nl (9)
- # clojure-spec (49)
- # clojure-uk (112)
- # clojurescript (50)
- # clojutre (4)
- # core-async (2)
- # cursive (4)
- # datomic (192)
- # emacs (10)
- # events (4)
- # figwheel-main (147)
- # fulcro (94)
- # graphql (5)
- # instaparse (1)
- # jobs-rus (1)
- # keechma (10)
- # leiningen (223)
- # luminus (3)
- # mount (23)
- # nrepl (8)
- # off-topic (44)
- # onyx (10)
- # pedestal (5)
- # re-frame (19)
- # reitit (8)
- # shadow-cljs (62)
- # uncomplicate (3)
I’m trying to figure out a way to intercept the error messages thrown by clojure and convert them to present something more useful for beginners. I’m struggling to find a viable strategy for CIDER REPLs.
I looked at having users start a sub-REPL, but this ticket indicates it won’t work with nREPL (so won’t work with CIDER) https://dev.clojure.org/jira/browse/CLJ-2040
my other option is to try to build out nrepl middleware? Or is there an approach I’m not considering. Some CIDER-specific configuration? Any pointers are appreciated
Middleware is probably the most viable option that I know of, Bohzidar will better answer but orchard
is now the place for "cider" logic while cider-nrepl
is for wrapping things into middleware. I say orchard
because it could easily be used with prepl
when it happens.
I can probably help with the cljs side once the idea is flashed out a bit. Opening an issue in cider
is probably a good idea to keep track of the conversation
With cider 18, what is the current solution for having a repl when you jump to the source of a library?
I usually do sesman-link-with-directory, but yeah it sucks that you have to do this manually
I use sesman-link-with-buffer. It sucks, but I've found that I don't do as often as I thought.
Edge has been redesigned around the local dependencies feature of edge, so we jump in a lot.
Also, what's the approach for selecting which figwheel build the clojurescript should connect to?