This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-13
Channels
- # aws-lambda (7)
- # beginners (80)
- # boot (134)
- # cider (11)
- # cljs-dev (5)
- # cljsjs (3)
- # cljsrn (19)
- # clojure (144)
- # clojure-austin (2)
- # clojure-berlin (3)
- # clojure-greece (6)
- # clojure-italy (3)
- # clojure-russia (95)
- # clojure-spec (57)
- # clojure-uk (120)
- # clojure-za (2)
- # clojurescript (71)
- # component (1)
- # css (1)
- # cursive (22)
- # datascript (2)
- # datomic (101)
- # dirac (9)
- # docker (3)
- # emacs (10)
- # events (2)
- # immutant (3)
- # leiningen (2)
- # om (63)
- # om-next (1)
- # onyx (6)
- # pedestal (55)
- # portland-or (3)
- # protorepl (2)
- # re-frame (30)
- # reagent (10)
- # ring-swagger (1)
- # rum (31)
- # spacemacs (5)
- # specter (9)
- # untangled (90)
- # vim (46)
- # yada (2)
debug-repl, https://github.com/gfredericks/debug-repl/blob/http-intercept/src/com/gfredericks/debug_repl/http_intercept.clj and https://github.com/SevereOverfl0w/.files/commit/10bedd44bc271e115c2c8e3ed665e7ae37471fd1 = debugging transquility
https://github.com/bpiel/sayid/issues/8 also looks like there's some interest in this coming to vim 🙂
Speaking of conj. A fun thing I stumbled across today: https://github.com/neovim/neovim.github.io/commit/0b58dda42e4b6ec50c0b7b8c3abda907e29afbc7#diff-a3610441ce5b5dc970a04b436631dadbR181
Good timing — been thinking about how to version this api client library. I do too, I’m reading some issues on Github re: api versioning and he seems to be a champion of simplicity.
Yeah. I always enjoy reading his rationales on things. Although things sometimes seem to be so obvious to him, and not obvious to others and he needs a little prompting in order to explain.
Took a while for him to put together his big post on why neovim's async api is better than vim8's (and it hugely is imo)
Google not turning up much, but I’m curious. You can hit Neovim’s RPC API w/ TCP or Unix Domain sockets, as well as STDIO.
@jebberjeb https://www.reddit.com/r/neovim/comments/58nrwv/neovim_api_comparison_with_vim_channels/d923cfu/
I wish I had an easier way to search reddit. This isn't the first time I've done this recently.
I didn't realise that neovim's api supported plain ol' things like stdio. That's cool.
Yes, when you use jobstart() to fire off a remote plugin (as a co-process), the plugin process can use STDIO as the channel.
Technically I suppose you can just telnet to a tcp socket and do it… If you’re fluent in messagepack 🙂
> Vim invented an ad-hoc protocol (it does not implement JSON-RPC) where JSON blobs can be sent over a channel and each blob has a request id and some other metadata. > In Vim a channel can have any protocol; this leaves quite a burden on the community to figure out a consensus. JSON also is very awkward (broken) for transporting binary data.
I always interact with neovim via my hex editor or something esoteric like that, right?
I think the JSON is parsed for you. I think that's why it has a request id, so vim can direct the message
yikes, remove VimL execution. Building a Clojure client for that would only be marginally better than a Clojure -> VimL compiler.