This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-29
Channels
- # 100-days-of-code (2)
- # bangalore-clj (1)
- # beginners (141)
- # cider (33)
- # cljs-dev (13)
- # cljsjs (7)
- # cljsrn (1)
- # clojure (88)
- # clojure-conj (3)
- # clojure-dev (24)
- # clojure-italy (11)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-sanfrancisco (1)
- # clojure-spec (4)
- # clojure-uk (53)
- # clojurescript (65)
- # core-logic (2)
- # cursive (28)
- # datomic (33)
- # duct (2)
- # emacs (3)
- # figwheel-main (9)
- # fulcro (44)
- # hoplon (6)
- # leiningen (144)
- # mount (1)
- # nrepl (21)
- # off-topic (102)
- # onyx (2)
- # other-languages (5)
- # pathom (6)
- # planck (3)
- # portkey (1)
- # re-frame (7)
- # reagent (5)
- # reitit (17)
- # shadow-cljs (24)
- # spacemacs (16)
- # tools-deps (64)
- # uncomplicate (2)
- # vim (22)
Hey, this reminds me. I have a need for an nREPL client that is thin and super light-weight, for CLI use. Well, not exactly for CLI use, but for use by an editor that is heavily bought into the idea of small tools and UNIX. Which means, I think, that the client needs to maintain persistent connection, by forking and forwarding.
I started hacking on a tool a few weeks ago (called rep
, because it doesn't l
). But never got it useful.
Vim loads python dynamically, so it can keep the connection open, I thought. Kakoune won't do that.
A bencode decoder can be written quite easily, I encourage you to continue with that path
OK. It's on hold for a couple weeks. I was actually wondering if anybody had done something like this.
I thought about it, but I came to the conclusion that such a thing would have to end up editor-specific, and wouldn't be an effective use of my time because of nvim's remote plugins.
So, in terms of the REPL window, it will write, pre-formatted to a fifo. But the client rep
command will return EDN or some such structured output.