This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-14
Channels
- # beginners (33)
- # boot (38)
- # clara (21)
- # cljs-dev (1)
- # cljsjs (2)
- # cljsrn (12)
- # clojure (230)
- # clojure-argentina (1)
- # clojure-brasil (3)
- # clojure-dusseldorf (4)
- # clojure-france (9)
- # clojure-italy (1)
- # clojure-russia (123)
- # clojure-spec (46)
- # clojure-turkiye (1)
- # clojure-uk (60)
- # clojurescript (83)
- # core-async (6)
- # cursive (10)
- # datascript (19)
- # datomic (28)
- # defnpodcast (1)
- # emacs (7)
- # figwheel (7)
- # fulcro (29)
- # leiningen (29)
- # lumo (9)
- # off-topic (14)
- # om (1)
- # onyx (25)
- # pedestal (1)
- # protorepl (3)
- # re-frame (10)
- # reagent (41)
- # ring-swagger (11)
- # shadow-cljs (10)
- # testing (5)
- # unrepl (3)
- # vim (3)
I'd like some feedback on the design of https://github.com/clojure-vim/vim-jack-in/commit/1ed927f7ec3430b510497842816872c1b2604270 because pending this change, I think that the plugin is "finished" except for updates.
The other feature I might add is the ability to dump the final commands out, so you can use them in a script ./lein repl
Concerns I have: - User's overriding versions, artifacts, etc. is important - Multiple plugins "depending" on cider-nrepl @ different versions (answer here might be to depend on fireplace/replant instead!) - Are artifact forks a problem? Maven doesn't handle this well, so maybe it doesn't make sense for me too either. - Should I look at deps.edn for inspiration around format - Should I provide functions to help manipulate the deps