This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-11
Channels
- # bangalore-clj (1)
- # beginners (24)
- # boot (134)
- # boulder-clojurians (2)
- # cider (3)
- # cljs-dev (2)
- # cljsjs (44)
- # clojars (9)
- # clojure (60)
- # clojure-greece (2)
- # clojure-quebec (1)
- # clojure-russia (44)
- # clojure-spec (15)
- # clojure-uk (1)
- # clojurescript (37)
- # core-matrix (1)
- # datomic (7)
- # emacs (1)
- # hoplon (154)
- # liberator (3)
- # mount (2)
- # om (20)
- # onyx (2)
- # pedestal (3)
- # planck (12)
- # re-frame (26)
- # reagent (32)
- # uncomplicate (4)
@mnewhook The Planck classpath mechanism is static, so the classpath itself cannot be changed at runtime, if that’s what you are asking. Having said that, there is no technical limitation that would preclude such a feature from being added.
I means that i need to futz with the inf-clojure-program
for each separate project I’m working which has an external dependency on which seems less than ideal
if only planck had nREPL support? 🙂 Is there anything precluding this support besides implementing it?
@mnewhook Right. Planck could support nREPL. Instead Socket REPL support was implemented.
mnewhook: I think you could solve this by adding a .dir-locals.el
file which contains your inf-clojure-program
for each project https://www.gnu.org/software/emacs/manual/html_node/emacs/Directory-Variables.html
Also, if there are improvements that could be made to the Emacs section of http://planck-repl.org/ides.html I'll take PRs relying on the community.
Planck 1.17 released https://github.com/mfikes/planck/releases/tag/1.17