This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-07
Channels
- # adventofcode (38)
- # aleph (1)
- # bangalore-clj (3)
- # beginners (126)
- # boot (165)
- # boulder-clojurians (5)
- # cider (42)
- # cljsrn (11)
- # clojure (203)
- # clojure-greece (6)
- # clojure-hk (1)
- # clojure-italy (11)
- # clojure-new-zealand (1)
- # clojure-nl (1)
- # clojure-russia (112)
- # clojure-spec (86)
- # clojure-uk (176)
- # clojurescript (38)
- # code-reviews (2)
- # core-async (2)
- # cryogen (2)
- # cursive (16)
- # datascript (2)
- # datomic (80)
- # events (2)
- # garden (28)
- # hoplon (115)
- # jobs (1)
- # jobs-discuss (7)
- # klipse (50)
- # lein-figwheel (15)
- # liberator (17)
- # luminus (6)
- # off-topic (8)
- # om (31)
- # onyx (26)
- # parinfer (4)
- # planck (35)
- # protorepl (26)
- # quil (2)
- # re-frame (50)
- # reagent (21)
- # ring (5)
- # rum (2)
- # schema (1)
- # untangled (29)
- # vim (10)
- # yada (40)
@juhoteperi thinking about doing something like this https://github.com/puredanger/replicant as a simple first swing at it. The plugin could inject code for this or a similar repl function, then fire up another socket repl server on a free port. Or, heck even shut down the original socket repl and start one up on the same port, using the new repl function. I’m not sure exactly how I feel about that approach. But I think it would be interesting to experiment with it.
Hmm, starting up another socket repl server sounds good
It easily use random port both editor and repl know about etc.
https://neovim.io/news/2016/11/ I jumped straight to fun, this is very interesting. Glad to see Lua is still coming
@jebberjeb That was a long time ago now. This newsletter is covering from about a year ago I think.