Fork me on GitHub
#cider
<
2016-02-23
>
cap10morgan01:02:46

I can’t imagine where I would be doing that

malabarba02:02:46

Either that or you have a special print-method defined for vars.

malabarba02:02:16

Does this happen consistently?

jonpither08:02:57

Can you spawn nrepl-middleware requests from within nrepl-middleware?

benedek08:02:31

I think u should be able to. And u should be able to define kinda chains of middlewares too but I could nor really figure that out. Sometimes worked sometimes did not

jonpither08:02:09

reading clojure.tools.nrepl.server, I can't quite see how nrepl-middlewares are setup in the first place

jonpither08:02:44

i.e., there's default-middlewares, but how do other ones get added

jonpither08:02:34

Ah, it's cider-nrepl-handler in cider-nrepl

benedek08:02:52

U either explicitly define them or for leinengen u can use a lein plugin for adding them

benedek08:02:12

Both cider and refactor-nrepl does that

jonpither08:02:36

You couldn't spawn a request from inside middleware, as the handler isn't def'd anywhere

benedek08:02:49

Boot is diff a bit as u don't have lein plugins obvs

jonpither08:02:02

TBH I don't really need to, but just from a theoretical perspective

benedek09:02:45

i meant :expects like :expects #{#'pr-values} (from cider-nrepl source) doc here: https://github.com/clojure/tools.nrepl#middleware-descriptors-and-nrepl-server-configuration

cap10morgan16:02:59

@malabarba: It happens every time, yes. I should look over my init.el again and see if I cargo-culted anything I didn’t mean to. simple_smile

cap10morgan16:02:10

@malabarba: looks like (setq cider-repl-use-pretty-printing t) was the culprit. is that expected behavior?

malabarba16:02:05

@cap10morgan: It's not. And it's not the first issue we have with the current pretty-printer

malabarba16:02:43

We also had some issue with defrecords not being printed appropriately

cap10morgan16:02:56

@malabarba: OK, I’ll file a bug.

malabarba16:02:39

Check out the one I linked

malabarba16:02:17

If you see the same behavior, add a comment there explaining what you observed instead of filing a new one

cap10morgan16:02:45

@malabarba: OK, will do.