This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-01
Channels
- # beginners (117)
- # boot (8)
- # cider (22)
- # clara (3)
- # clojure (79)
- # clojure-italy (3)
- # clojure-spec (34)
- # clojure-uk (34)
- # clojurescript (74)
- # cursive (7)
- # datascript (5)
- # datomic (28)
- # defnpodcast (1)
- # dirac (9)
- # docker (25)
- # duct (1)
- # emacs (14)
- # fulcro (67)
- # graphql (1)
- # hoplon (15)
- # jobs (4)
- # juxt (6)
- # off-topic (76)
- # parinfer (3)
- # re-frame (25)
- # reagent (4)
- # rum (6)
- # shadow-cljs (1)
- # spacemacs (30)
- # sql (15)
- # unrepl (36)
- # yada (1)
I don’t know if anyone here is familiar with the internals of CIDER but is it possible to get details of project.clj?
or this one, which is more recent https://github.com/clojure-emacs/parseclj
cider doesn't mess with project.clj except to modify the lein command to include its middleware (as far as i know). project.clj is really a lein thing and just knows enough to crank up a lein repl
What I’m thinking of doing is not editing the file but getting some information from the file to inform the behavior of CIDER
I’m trying to see what the project.clj is targeting and suggest to the user the possibility of using that as a REPL backend instead of Rhino
Hi folks, how can I avoid the "var risky" question when I am doing something like the following in .dir-locals.el
?
((nil . ((projectile-test-suffix-function . #'projectile-lumo-test-suffix)))