Move to a Vundle based distribution

[devinus]

@eMxyzptlk Have you had any thoughts regarding this? It seems at some point Vundle's author even did a proof of concept using Janus.

[kalbasit]

I have thought about it but I have no immediate plans to actually start experimenting with it (not much time on my hands at the moment), my only concern is we, Janus Maintainers, won't have control on the plugins versions and thus we cannot guarantee that all the plugins are working properly, but that might change, @gmarik is planning add that feature, see Vundle's Readme

[a-b]

+1 I'd love to see vim-janus based on vundle @gmarik `s stuff rock!

[helps]

good news

[a-b]

Yeah! Thanks!

[a-b]

Any updates there?

[kalbasit]

Since Vundle's todo still lists allow specify revision/version? as not done, we can't move on with this

[pioneerit]

Almost a year? Any updates?

[kalbasit]

The item allow specifying revision/version? still marked as not done in the todo of Vundle's Readme so this isn't going anywhere.. sorry.

[Shougo]

neobundle is fork of Vundle, but it is almost rewrited. It supports version lock feature.

https://github.com/Shougo/neobundle.vim

[kalbasit]

This sounds interesting, I will look into it

[a-b]

I think it worth to consider neobundle as package manager http://gmarik.info/blog/2014/02/04/why-i-stopped-contributing-to-vundle @Shougo is there any specific reason to make clone instead of pull request back to the vundle?

[Shougo]

@Shougo is there any specific reason to make clone instead of pull request back to the vundle?

It is yes. I want to add several features. See the differences neobundle from Vundle.

To decide to use neobundle or vundle, you should compare features.

[aemonge]

Still no Vundle version ?

[dd1994]

neobundle.vim is awesome.

[kalbasit]

Not before gmarik/Vundle.vim#35 is done

[pmorch]

I'm a little new to these plugin managers, but it seems Vundle is now inactive. Would NeoBundle be a better choice for that reason alone? NeoBundle already can peg stuff at a particular rev.

[aemonge]

+1 pmorch

[a-b]

It worth to explore https://github.com/junegunn/vim-plug too.

[kalbasit]

Vim-plug is actually pretty cool, it also support branch/tag.

[aemonge]

I've tried NeoComplete as well. It's more complicated than Vundle. In my own distro I'm also using Vundle ( https://github.com/aemonge/dotFiles/blob/master/.vimrc ). I think it's better and simpler.

[brodock]

vim-plug if you use neovim does some crazy async operations which doesn't slow vim down

[chauncey-garrett]

NeoBundle is now inactive and has been replaced with Dein.

Vim-plug offers, among other things, branch/tag/commit support, on-demand loading, and post-update hooks; all of which I think fit within Janus' ideology.

[brodock]

I have re-implemented with vim-plug "most" of the janus I use. If anyone wants to try, it's started as a PoC, but it's serving me well for many months already. Hope it could be useful or perhaps be used as a startpoint / prototyping of a new "vim-plug" based janus.

https://github.com/brodock/janus-plugged (only NeoVim is supported by now)

[kalbasit]

@brodock why not submit a Pull Request to Janus rather than creating a fork? I intended to do that for a long time now, just my time is very limited lately and I'd appreciate a PR for this.

[brodock]

@kalbasit When I started I had literally no vim scripting knowledge, and I wasn't sure how well would this work or not, so it started as a PoC. There are so many "custom" things janus implement, that I just don't have the bandwidth to actually lead this migration. On top of that, no official word has been made on this topic until today.

I'm happy to help this effort and to bring ideas if this is the direction we are going to take.

[kalbasit]

@brodock my apologies for not having made this clear before (pretty busy lately). I am hoping I will have some bandwidth at the start of 2017 and I would like to start from scratch in a new branch, mostly based on your work. Let me know if you'd like to be included in the development efforts.