This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-18
Channels
- # boot (42)
- # cider (26)
- # cljs-dev (6)
- # cljsrn (6)
- # clojure (119)
- # clojure-berlin (3)
- # clojure-dev (2)
- # clojure-nl (1)
- # clojure-russia (38)
- # clojure-spec (1)
- # clojurescript (44)
- # component (3)
- # cursive (1)
- # data-science (2)
- # datomic (19)
- # dirac (60)
- # emacs (12)
- # figwheel (2)
- # hoplon (13)
- # iot (4)
- # keechma (2)
- # klipse (38)
- # leiningen (5)
- # luminus (1)
- # lumo (1)
- # off-topic (6)
- # om (2)
- # om-next (4)
- # onyx (21)
- # perun (79)
- # reagent (32)
- # untangled (39)
- # vim (36)
- # yada (1)
@hans: So before the timeout occurs C-g
and check *nrepl-server <whatever>*
, paste that here
@arrdem the nrepl-server buffer contains nothing but nREPL server started on port 45287 on host 127.0.0.1 -
is cider and dirac incompatible? cider wants its middleware; dirac seemsto want NO OTHER middleware
is restarting cider when used with figwheel and clojurescript supposed to work out of the box with cider-restart
?
I mean I do a cider-jack-in-clojurescript
, then I update the dependencies and want to get it updated, so I do cider-restart
but it restarts only the JVM repl
not the clojurescript one
or there is another magic solution?
also there is no integration for running clojurescript tests with lein doo phantomjs
right?
I can probably do something easily anyway to just have the running process in Emacs, but I was wondering if there was already
@andrea.crotti no, the restart only takes care of namespace/vars reloading. If you want to add deps dynamically you need to use something specific for classloader hotload. Also another thing you can check if you use boot
is https://github.com/danielsz/system
It tries to reload namespaces when necessary as well as restart the repl when you need to.
Also, hotload dependencies in boot
is only a call to boot.aether/add-dependency
if I recall correctly
restart should restart all repls. unfortunately, cljs repls are started by a callback and this callback isn't maintained. so restart doesn't know to call that clojurescript invocation
Ah ok makes sense
But it could just kill all the Clojurescript repls easily I think
Even just by killing buffers that match a regexp
I can't really use a Clojurescript repl after I change dependencies and restarted anyway right?
Just a bit of elisp that kills everything and does the jack in again might do the trick already
But if a new dependency added is only used by Clojure and not Clojurescript then I don't have to restart the Clojurescript repl right?