Fork me on GitHub
#cider
<
2015-11-24
>
agile_geek07:11:51

@bozhidar: Looking forward to the announcement. Would be great if you could ‘unveil’ 0.10 at ClojureX (no pressure!) 😉

bozhidar08:11:07

@agile_geek: I’ll do my best

bozhidar08:11:53

if the slides are not the great, you’ll know I put more effort into wrapping 0.10 simple_smile

bozhidar08:11:56

and yes - the typos I make are always amazing simple_smile

bozhidar08:11:10

btw, if someone wants to help with the release that’d be pretty awesome

bozhidar08:11:47

most of the tickets on the first page are not particularly complex

bozhidar08:11:09

and it’d be nice to get as much goodness as possible into 0.10

malabarba13:11:08

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

jonpither19:11:53

The session in the message passed to nrepl middleware handlers has become a big atom

jonpither19:11:01

rather than a string

jonpither19:11:18

is there a way to easily get the string session ID?

jonpither19:11:58

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

jonpither19:11:00

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?

benedek19:11:39

@jonpither for the separate nrepl-client see: https://github.com/clojure-emacs/cider/issues/1225

malabarba20:11:14

@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.

jonpither20:11:31

Thanks @malabarba @benedek - both answers are helpful

waffletower22:11:11

OMG I can't believe how much less annoying CIDER is knowing that you can simply press 'q' to dismiss an exception trace buffer

waffletower22:11:33

Hopefully well on my way now to disagreeing with https://gist.github.com/levand/b1012bb7bdb5fcc6486f

waffletower22:11:19

And hopefully the buffer autofocus behavior will remain the default so I don't have to relearn how to deal with it simple_smile

malabarba22:11:23

Glad to hear

malabarba22:11:09

At least one of the points there has actually been addressed already. And some are misconceptions, IMO.

malabarba23:11:24

But most are just opinions related to that person's workflow. Which is fair. Sometimes you can't be the best at everything. :relaxed:

malabarba23:11:08

But I'd be willing to know if any of the complaints there affect other people too.

benedek23:11:22

i think i just use

;; error buffer not popping up
(setq cider-show-error-buffer nil)
in my cider config and only switch to the error buffer when i want to know the details