This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-01
Channels
- # beginners (41)
- # boot (25)
- # cider (34)
- # cljs-dev (221)
- # cljsrn (1)
- # clojure (191)
- # clojure-dusseldorf (4)
- # clojure-hamburg (1)
- # clojure-italy (8)
- # clojure-poland (1)
- # clojure-russia (22)
- # clojure-spec (27)
- # clojure-uk (91)
- # clojurescript (101)
- # core-async (11)
- # cursive (33)
- # data-science (9)
- # datascript (3)
- # datomic (30)
- # emacs (4)
- # events (4)
- # garden (6)
- # jobs (3)
- # leiningen (8)
- # luminus (39)
- # lumo (2)
- # off-topic (158)
- # om (13)
- # onyx (1)
- # parinfer (22)
- # planck (2)
- # protorepl (5)
- # re-frame (7)
- # reagent (10)
- # remote-jobs (1)
- # ring (1)
- # ring-swagger (20)
- # unrepl (92)
- # vim (11)
@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
I found it super useful the last time 🍻
Same here 🙂
What are the general concerns/limitations with fireplace and what are the hopes for the next incarnation?
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.
* hotloading a sourcefile from outside the fireplaces#sessions path into a nrepl connection
I'd be up for creating a document somewhere and doing some collection of requirements / irks with Fireplace.
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.