This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-11
Channels
- # admin-announcements (26)
- # aws (1)
- # beginners (356)
- # boot (28)
- # cider (20)
- # clara (12)
- # cljs-dev (78)
- # cljsrn (22)
- # clojure (333)
- # clojure-brasil (1)
- # clojure-dev (15)
- # clojure-miami (1)
- # clojure-nl (3)
- # clojure-russia (61)
- # clojurecup (3)
- # clojurescript (137)
- # clojurex (4)
- # core-async (4)
- # data-science (3)
- # datavis (2)
- # datomic (31)
- # editors (1)
- # emacs (9)
- # hoplon (3)
- # juxt (8)
- # ldnclj (47)
- # leiningen (4)
- # luminus (4)
- # off-topic (20)
- # om (332)
- # onyx (1)
- # parinfer (23)
- # portland-or (4)
- # proton (161)
- # reagent (46)
- # ring-swagger (11)
- # specter (7)
- # yada (2)
@snoe @bhurlow, I suppose the only difference between the nvim and vim implementations is the placement of logic in js vs viml
but it seems like both can interface with Node well
and snoe has done great work with the diff part
I wonder if the projects could be merged somehow. I didn’t think something like this could be done in vim classic
@shaunlebron @snoe’s approach is definitely a much richer implementation than mine. I’m not really using nvim as my standard editor and for some reason the nvim node-host seems incomplete to me. In general I like the idea of offloading as much logic as possible to the parinfer lib as viml can be rocky at times and js editors are probably the future
That being said, the basic rpc approach that I’m working on in vim-parinfer is working really nicely as a general tool. I don’t even really need paredit or vim-sexp anymore
I’ll take another look at @snoe’s lib and see if perhaps they could be adapted together or something
I became interested in trying this after seeing: https://github.com/edpaget/parinfer-mode
snoe has more logic in cljs and is doing some diffing logic in it in order to pass the correct information to the parinfer lib
but you’re both offloading to the parinfer lib in the same way
i do like that snoe’s implementation is in cljs, and i like that bhurlow’s plugin works without requiring nvim
@bhurlow you are very correct about the limitations of node-host, I've been pushing more and more into viml lately.
but yes, I can’t kick the vim habit either..
as far as neovim vs vim though, I haven't noticed anything missing from neovim, it's quite stable and the switch was kind of seamless.
I’m used to my macvim window
never figured out how to get neovim to work with that
@hmadelaine: nice! sorry I missed this yesterday
adding this to the website now