This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-15
Channels
- # beginners (138)
- # bigdata (2)
- # boot (45)
- # cljsrn (29)
- # clojure (108)
- # clojure-austin (1)
- # clojure-gamedev (1)
- # clojure-korea (9)
- # clojure-russia (50)
- # clojure-spec (2)
- # clojure-uk (28)
- # clojurescript (40)
- # component (1)
- # cursive (35)
- # datomic (39)
- # dirac (16)
- # emacs (22)
- # flambo (11)
- # funcool (6)
- # hoplon (74)
- # leiningen (4)
- # off-topic (1)
- # om-next (2)
- # onyx (141)
- # planck (7)
- # proton (10)
- # protorepl (4)
- # re-frame (21)
- # reagent (13)
- # remote-jobs (1)
- # ring (3)
- # specter (9)
- # sql (3)
- # test-check (14)
- # untangled (1)
- # vim (9)
- # yada (16)
I think that asciicast/screencast showing some of the features as part of guide would be great
dominicm I have a docker box setup with neovim and other goodies. I think that kind of pre-packaged env could have some traction instead of do it yourself installation from scratch each time. Was that the thing you were thinking of?
I was thinking of either a .config/nvim you download, or taking advantage of the package feature in vim8
+1 for having this as a .config/nvim, using docker seems like a massive overhead for this
As long as one could bootstrap the plugin manager with the .config/nvim setup, this looks fine for me
Also, vimscripts can be sourced, so we could provide something like:
" clojure-nvim.vim-plug.vim
Plug "hkupty/acid.nvim"
Plug "clojure-vim/async-clj-omni"
" User script
source $HOME/.config/nvim/clojure-nvim.vim-plug.vim
And just in case: https://github.com/reborg/docker-boxes/blob/master/03-try-neovim.dockerfile