Fork me on GitHub
#vim
<
2017-08-01
>
zamaterian11:08:50

@dominicm sound like its time for you to write a little blogpost again, with your workflow and maybe a little status all the stuff happening with clj/cjls in nvim

zamaterian11:08:22

I found it super useful the last time 🍻

dominicm12:08:07

I should try & get something a bit more concrete before I do that I think 😛

dominicm12:08:45

My daily driver is still vim-fireplace

zamaterian12:08:49

Same here 🙂

Jarrod Taylor (Clojure team)13:08:05

What are the general concerns/limitations with fireplace and what are the hopes for the next incarnation?

dominicm13:08:55

Big things I notice: * Fallen behind cider-nrepl, e.g.: things like specs, see-also, etc. have been added to docs, but fireplace doesn't use them * Async as standard would be nice for tasks such as find-usages or code completion Not sure there's really much more. There's a lot of little things that are missing, pprinting is another.

zamaterian13:08:34

* hotloading a sourcefile from outside the fireplaces#sessions path into a nrepl connection

dominicm13:08:35

that doesn't work? what happens?

dominicm13:08:55

I'd be up for creating a document somewhere and doing some collection of requirements / irks with Fireplace.

Jarrod Taylor (Clojure team)14:08:48

I have a bit of a backlog I'm working through at the moment, but I'd be down for contributing to new tooling if collaboration on something makes sense. I'm very much interested in seeing Vim/NeoVim minimally keep up in this space and it would be great to innovate some as well.