This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-19
Channels
- # beginners (7)
- # boot (48)
- # clojure (50)
- # clojure-portugal (1)
- # clojure-russia (10)
- # clojure-spec (29)
- # clojure-uk (9)
- # clojurescript (116)
- # core-logic (1)
- # cursive (12)
- # datascript (2)
- # datomic (7)
- # defnpodcast (8)
- # dirac (80)
- # emacs (486)
- # hoplon (5)
- # instaparse (3)
- # keechma (1)
- # luminus (3)
- # lumo (35)
- # off-topic (65)
- # om (6)
- # onyx (6)
- # perun (42)
- # re-frame (5)
- # reagent (5)
- # rum (2)
- # untangled (170)
- # vim (13)
It's like spacemacs vs. emacs - do you want to build your own custom editing experience?
a lot of the time I prefer the freedom to only include parts of a dev environment that I'm using
@dominicm what's your experience using node-host nvim plugins? Is it a stable platform to write tools with?
@mikepjb node-host has broken quite a lot, @snoe has had a lot of problems keeping his cljs plugins stable on it. Although, I think most of the breakage was from msgpack encoding bugs which are ironed out now. I don't think there's been much breakage in a while now.
Definitely a great idea, with callbacks for each incoming message & the streams api make it pretty ideal.
The drawback is a dependency on the npm/node ecosystem being installed on your system.
@mikepjb I think there's still a problem somewhere in the node-host chain. https://github.com/clojure-vim/nvim-parinfer.js/issues/30#issuecomment-280381472