This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-24
Channels
- # admin-announcements (25)
- # beginners (132)
- # boot (89)
- # cider (26)
- # clara (12)
- # cljs-dev (10)
- # cljsrn (11)
- # clojure (151)
- # clojure-germany (8)
- # clojure-russia (1)
- # clojurescript (137)
- # cursive (33)
- # datavis (28)
- # datomic (3)
- # devcards (8)
- # hoplon (5)
- # immutant (11)
- # jobs (4)
- # ldnclj (58)
- # lein-figwheel (7)
- # off-topic (95)
- # om (114)
- # onyx (91)
- # parinfer (38)
- # portland-or (1)
- # re-frame (26)
- # reagent (1)
@bozhidar: Looking forward to the announcement. Would be great if you could ‘unveil’ 0.10 at ClojureX (no pressure!) 😉
@agile_geek: I’ll do my best
In particular, we have a lot of low-hanging-fruits that would make very noticeable UX improvements. https://github.com/clojure-emacs/cider/labels/low%20hanging%20fruit
The session in the message passed to nrepl middleware handlers has become a big atom
Also, is there a plan in CIDER to make the nrepl-client.el a separate lib? I see that there is a cider-client, so clearly there's a layered approach
Hmm, I guess the session being an atom, you no longer need a session ID string (where you'd probably manage your own sessions). This feels a good change, is there any doc on how this works for nrepl-middleware coders?
@jonpither for the separate nrepl-client see: https://github.com/clojure-emacs/cider/issues/1225
@jonpither nrepl itself changes the string to an atom in its session middleware. It's been like that for as long as I know. You can make your middleware act before or after the session middleware by using an :expects or :requires keyword. You can also get the string ID from the atom's metadata.
Thanks @malabarba @benedek - both answers are helpful
OMG I can't believe how much less annoying CIDER is knowing that you can simply press 'q' to dismiss an exception trace buffer
Hopefully well on my way now to disagreeing with https://gist.github.com/levand/b1012bb7bdb5fcc6486f
And hopefully the buffer autofocus behavior will remain the default so I don't have to relearn how to deal with it
At least one of the points there has actually been addressed already. And some are misconceptions, IMO.