This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-18
Channels
- # aws-lambda (3)
- # beginners (57)
- # boot (3)
- # bristol-clojurians (1)
- # cider (38)
- # cljs-dev (23)
- # clojure (35)
- # clojure-italy (32)
- # clojure-nl (6)
- # clojure-spec (35)
- # clojure-uk (132)
- # clojurescript (34)
- # cursive (22)
- # data-science (1)
- # datomic (54)
- # devcards (1)
- # duct (5)
- # editors (7)
- # euroclojure (4)
- # fulcro (40)
- # graphql (1)
- # hoplon (6)
- # immutant (5)
- # jobs (1)
- # off-topic (22)
- # om (1)
- # planck (17)
- # portkey (1)
- # protorepl (12)
- # re-frame (97)
- # reagent (67)
- # reitit (16)
- # ring-swagger (1)
- # shadow-cljs (98)
- # spacemacs (8)
- # sql (20)
- # tools-deps (60)
thanks for the hard work guys, upgrading now eager to try out the new session manager. 🙂
I am working on a new CLJS-only project. In my project.clj
I hit C-c M-J and select Figwheel among the options. If I hit C-c C-z from a CLJS file I can see the REPL as expected. But if I open dired and navigate to a CLJS file, hitting C-c C-z from the REPL brings me back to dired instead of the CLJS file I was visiting. Do you want me to open an issue on GitHub?
also, there is no indication in the REPL buffer that this is a CLJS REPL. I mean, the buffer name shows clj
even though I can interact with Figwheel from it.
moreover, in the modeline the indicator always shows cider[not connected]
even after C-c M-J.
I keep getting these kinds of traces in emacs when editing clojurescript code, after upgrading Emacs + prelude:
@borkdude you can file a ticket about this if you want. there are ways to suppress errors from the debugger i think if they are really just kinda logical ones
reporting about the new changes, OOTB C-c M-J
does the right thing for me, creating only one REPL asking for which CLJS one to start right after
I would say, AWESOME !
little behavior change is that cider-default-cljs-repl
is not taken into consideration
opened an issue
@richiardiandrea @bozhidar haven't tried the new changes but wondering about futher parameterization when starting a CLJS REPL, I.E. so that folks can further specify a build
@bhauman That’s really easy to do even now - we can just prompt users for the build. The thing that’s tricker is to be able to offer them some completion about the available builds - we should know where can we extract them from.
I don't know if you pull data from the project.clj already but the best way is to define a deproject
macro and then load the project.clj file
my idea when I had the cider-figwheel.el
main namespace was to add a parser eventually there
cannot commit time at the moment but we'll see
Since updating, I've started seeing flickering in clojure and cider
buffers - it seems to be el-doc
related; that is, it goes away when I deactivate el-doc
in that buffer, and then seems to stay good for a while before starting again. I'm not blaming this on cider
so far, because I've changed a bunch of other stuff including compositor, window manager, etc, over the weekend, and I build a new emacs every week from master. But I'd be interested if @bozhidar you can think of a mechanism for cider
causing this, or if anyone else sees it.