This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-18
Channels
- # aws (3)
- # beginners (18)
- # boot (3)
- # cider (47)
- # clara (54)
- # cljs-dev (62)
- # clojure (104)
- # clojure-berlin (1)
- # clojure-denver (1)
- # clojure-italy (1)
- # clojure-nl (22)
- # clojure-russia (30)
- # clojure-spec (28)
- # clojure-uk (95)
- # clojurescript (31)
- # cloverage (1)
- # cursive (1)
- # datomic (17)
- # duct (4)
- # emacs (27)
- # fulcro (36)
- # graphql (1)
- # hoplon (1)
- # jobs-discuss (1)
- # lein-figwheel (1)
- # lumo (2)
- # off-topic (44)
- # om-next (5)
- # onyx (29)
- # precept (1)
- # re-frame (8)
- # reagent (7)
- # ring (1)
- # ring-swagger (2)
- # schema (4)
- # shadow-cljs (185)
- # spacemacs (21)
- # specter (59)
- # tools-deps (7)
- # vim (15)
- # yada (1)
@bozhidar perhaps the best approach is to open an nrepl server inside my game and then cider-connect
to it? not sure if there’s feature parity with the repl using that approach
@dpsutton which deps?
a higher level question would be - if I use cider-connect
can I still do everything as expected - aka, change code and reload it while it’s running, etc
Yes. Cider just invokes lein (or whatever) and will speak to that nrepl server. It's deps add and modify some operations in the nrepl communication to add it's features
I'm looking for the exact deps you need right now. It should be more clear in the read me or the docs. But I think you can just include cider-nrepl without a version that matches your CIDER client version
I mean without any cider dependencies it can just bare nrepl eval and work with the code
Should be up top. There's a section that talks about cider connect but not the thing to include if you want a full experience
Yeah, few things work without the extra middleware, but eval
is certainly one of them.
what's the best/recommended way to run tests in emacs then? have an eshell window open ?
And I hope we’ll port the test-related functionality to cljs soon, but we aren’t there yet unfortunately.
What's the story with cider.el, clojure cli and clojurescript? Edge is gaining a set of instructions that I don't want to maintain.
https://github.com/juxt/edge/blob/master/app/README.adoc#clojurescript See the "tip"
Ah I just realized why there's a big slow down for @bhauman with his large reader forms. The font lock for locals backs up to include the top level form so it can know the locals. And with his large forms this is incredibly slow since it recurses onto subforms. I don't know why it's new but maybe we could inhibit this widening of scope
Hummmmmmm being less dumb here would actually be really hard. Is there at least a buffer-local people can use to toggle this behavior off?
@dominicm Yeah, it’s possible of course. I actually planned to tackle this when the whole nREPL transfer thing came along and then I decided that cleaning up nREPL and fixing some problems there is probably more important in the grand scheme of things.
Sure, I'm not trying to prioritise this on your list. Asking if there's reasons it isn't done, technical blockers.
Basically I just plan to augment the deps when doing cider-jack-in-cljs
and that should be enough.
Does cider-jack-in-cljs always prompt for how to create the sibling repl? In the case of t.d.a/edge there isn't really a standard way to get the running figwheel.
It prompts unless you set the variable cider-default-cljs-repl
. If it’s non-nil CIDER will just use its value for the sibling REPL.
Another thing I’m planning to change is creating two repls always - probably many people need just a cljs REPL and the second REPL is kind of redundant for them.