Fork me on GitHub
#vim
<
2016-11-15
>
zamaterian07:11:16

I think that asciicast/screencast showing some of the features as part of guide would be great

reborg11:11:16

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?

dominicm11:11:59

I was thinking of either a .config/nvim you download, or taking advantage of the package feature in vim8

mikepjb12:11:39

+1 for having this as a .config/nvim, using docker seems like a massive overhead for this

hkupty13:11:21

As long as one could bootstrap the plugin manager with the .config/nvim setup, this looks fine for me

hkupty13:11:58

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

reborg13:11:56

Which is just a starting point, because I still need to cleanup much stuff specific to my setup. But that shouldn’t take long time.

dominicm21:11:20

It's a neat idea, I've heard of doing this. Isolating all the software