This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # bangalore-clj (1)
- # beginners (29)
- # boot (13)
- # braveandtrue (5)
- # clara (5)
- # cljs-dev (42)
- # cljsrn (7)
- # clojure (55)
- # clojure-france (46)
- # clojure-nl (11)
- # clojure-portugal (1)
- # clojure-russia (268)
- # clojure-spec (26)
- # clojure-uk (32)
- # clojurescript (173)
- # clr (2)
- # core-async (46)
- # cursive (22)
- # datomic (33)
- # devcards (1)
- # emacs (5)
- # events (8)
- # figwheel (2)
- # flambo (4)
- # instaparse (8)
- # jobs (11)
- # klipse (46)
- # lein-figwheel (3)
- # london-clojurians (2)
- # nrepl (1)
- # off-topic (29)
- # om (4)
- # om-next (8)
- # pedestal (3)
- # rdf (4)
- # re-frame (51)
- # reagent (104)
- # remote-jobs (1)
- # rum (4)
- # schema (2)
- # specter (19)
- # untangled (16)
- # vim (52)
Hey guys, I’ve been working on an asynchronous repl tool like fireplace for vim, feel free to have a look https://github.com/michaelbruce/vim-link
We should probably all try & convene at some point and agree on a good approach to this async nrepl stuff 😛
@mikepjb Feel free to use https://github.com/clojure-vim/nrepl-python-client as a submodule for python stuff, It's pretty well battle tested now
A lot of bencode implementations I found (including the one I forked from) didn't handle utf-8 properly.
ah thanks @dominicm I’ll have a look - I’m using vim 8 at the moment so I’m not sure whether this plugin is compatible?
nrepl-python-client is a generic python client. It's not coupled to vim8/neovim/anything
@mikepjb out of interest why VimL8? (I tease only of course, particularly now I know we share a British sense of humour which is built on sarcasm)
Actually, more I think about it, the nrepl-python-client is really good for vim8, because of the generic channels feature.
I found nvim to be subpar - embedded terminals have performance issues, you cannot configure control over external programs like selecta (which I use as a fuzzy searching tool) easily
If you created a watcher & hooked it up to Vim's er... is it JSON-RPC-like or something? If you hooked it up to that you could do some really interested core.async-like stuff.
Interesting what you say about the external programs… Selecta is very similar to Fzf, which does work in Neovim, though I think there was some tweaking to make it so. So I can understand that.
yeah nvim is an interesting project, I can’t imagine it’ll be too long before I jump ship
I think there's an issue on the fzf gh where there's a reference to the surprisingly small amount of changes it required to fzf.
I really like the ability to write plugins using clojurescript and hosting on nodejs that’s pretty exciting
I think the general sentiment about the breaking compat change that the neovim made was that: - Vim never gave guarantees on STDIN - GVim doesn't actually work with STDIN
Especially now lumo is a thing, that would be a really interesting way to build an nREPL client.
yeah I’d been toying around with bootstrapping with lumo to install arch https://github.com/michaelbruce/arch-installer/blob/master/install.cljs
Oh neat! Here at JUXT @malcolmsparks has been using it to write Mach for deploying infrastructure & building— ah you know 😛
@jonpither is currently building https://github.com/juxt/roll to work with Mach as well.
yeah @malcolmsparks showed us a little bit during his yada talk at codenode
I'm guessing so, I wasn't able to get a particularly solid answer about what it was 😛
The policy in JUXT is that all projects must be 4 chars. So that shortening makes sense.
https://github.com/oliyh/martian by a JUXTer, but not JUXT.
Only major project still about that doesn't conform is Joplin. Which is somewhere between JUXTer & JUXT project.
Given that Python seems to be the most popular way to be doing vim + nrepl, I'll throw this in as a "no dependencies required" example of what I've been playing with: https://github.com/SevereOverfl0w/clojure-check which is based on Go, so you could just grab a binary for your platform.