This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-23
Channels
- # beginners (63)
- # cljs-dev (1)
- # cljsjs (1)
- # cljsrn (11)
- # clojure (208)
- # clojure-berlin (2)
- # clojure-dusseldorf (5)
- # clojure-italy (5)
- # clojure-norway (56)
- # clojure-russia (7)
- # clojure-spec (85)
- # clojure-uk (27)
- # clojurescript (191)
- # core-async (73)
- # cursive (4)
- # datomic (62)
- # defnpodcast (1)
- # hoplon (2)
- # jobs-rus (1)
- # juxt (14)
- # keechma (1)
- # leiningen (1)
- # lumo (126)
- # off-topic (2)
- # om (11)
- # onyx (27)
- # pedestal (52)
- # planck (21)
- # powderkeg (1)
- # re-frame (32)
- # reagent (14)
- # ring-swagger (1)
- # rum (3)
- # slack-help (19)
- # specter (23)
- # untangled (32)
- # vim (7)
- # yada (43)
The one-time startup cost of a Clojure plugin (via https://github.com/clojure-vim/neovim-client) is a pain. To be fair, I chose Clojure over ClojureScript for neovim-client mainly because I am more familiar with the libraries I'd need to do MessagePack-RPC, Socket IO, and other odds and ends, in Clojure/Java. It got me to a working prototype more quickly. I'd love to port it to ClojureScript. I agree, for many (most?) plugins, a slow to start, heavyweight Java process probably isn't a good fit. For a plugin that's integrating with a Clojure REPL, evaluating code, doing IDE-like tasks I'm not sure it's really a deal breaker. I've used clojure-socketrepl.nvim exclusively in my day job for about 50/50 Clojure & ClojureScript development for about 2 months now, and I really don't feel startup cost at all. Also, after using neovim-clojure to build clojure-socketrepl.nvim, I can confirm that using Clojure to write a non-trivial plugin was an awesome experience. Using the plugin to develop itself live was neat.
morning! Do you know a plugin that can indent Clojure code "tabbing" into columns (instead of basic formatting of Lisp code)?
vim-lion? 😄 or maybe https://github.com/junegunn/vim-easy-align