whats considered a good set of plugins for clojure development these days? at the moment I’m only using ‘guns/vim-clojure-static’ and ‘tpope/vim-fireplace’

Those cover most of what you need, I can recommend https://github.com/SevereOverfl0w/vim-replant as a good way to further integrate IDE features. https://github.com/eraserhd/parinfer-rust to get parinfer in vim (web demo here: https://shaunlebron.github.io/parinfer/demo.html) and https://github.com/clojure-vim/async-clj-omni/ for automatic omnicompletions via deoplete and ncm

disclaimer, I wrote replant and async-clj-omni

I just posted this a few days ago: http://endot.org/2018/07/14/vim-clojure-dev-2018/

Structural editing (vim-sexp) is wonderful.

ahh, thats the third plugin that I’m using vim-paredit at the time I was looking at vim-sexp it didn’t support enforced balancing of the parenthesis

Has anybody implemented the cider-nrepl debugger on top of fireplace yet?

Nope, I looked but the api is not very clear, I think it uses a side-channel.

I was kinda thinking I might cheap out and go for scope-capture instead.

I'm trying that out, too.

@eraserhd let me know how that goes, I'm interested in adding "native" support to replant in some way (however that looks)

The thing I thing would be really cool, honestly, would be if it would write and set up a deftest... But yeah. Using it feels a bit awkward at the moment, but I have the theory that it might get better if I stick with it.

Scope capture is magic. I’ve used it twice, to great effect each time.

The problem I have is mostly how to target the right invocation when I drill down.

Doesn't look like there's much in scope-capture to integrate. I wish there was a "list invocations" op

Then I could generate a buffer or something to auto-switch.

That would be cool.

https://github.com/vvvvalvalval/scope-capture/blob/master/src/sc/api.cljc#L189 an op could be added using this

it would be good to update scope-capture-nrepl to use the new nrepl at the same time

Having the line/column info is super cool

Is it standard here to have functions manipulating global state used by the middleware in nREPL?

nope

you should use dynamic vars

hmm. I'll have to figure out nREPL a bit better one of these days.

then you have sessions which manage the state for you

sessions?

https://juxt.pro/blog/posts/nrepl.html covers this a bit 😄

queued for studying, thanks

I think I would have approached the nrepl integration differently than Val did :thinking_face: he's literally trying to turn (+ 1 1) into (letsc (+ 1 1)) when doing :Eval or cp

Having said that, I'm not entirely sure how I would do it.

Oh, the way he's done it makes it work better with fireplace, ironically.

Oh, I see why it's that way... hmm, yes.

It's a bit concerning that he does (pr-str) on the code, I'm not sure that's lossless.

I think sc.nrepl.repl/in-ep needs to change the REPL prompt.

I'm not even sure that's doable in nREPL.

what do you mean, "change the REPL prompt"?

why does it need to?

maybe something like

dev=> (sc.nrepl.repl/in-ep 42)
dev+42=> _

in-ep also confuses fireplace.

I've seen stuff that confuses fireplace before too

it's a bit, meh.

I don't think the REPL prompt has to change.

I keep wanting, instead of like datawalk, just an nREPL middleware that replaces large subexpressions with, like ..1 and ..2 etc, and defines those.

like unrepl, but for nrepl? 😄

hmm, maybe that's where I got it