-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration to vim-plug #864 #866
base: master
Are you sure you want to change the base?
Conversation
Rename Vundle module to VimPlug
- Rename files - Change plugin action Bundle -> Plug Signed-off-by: Nanda Lopes <nandalopes@gmail.com>
- plugged.vim -> plugins.d/main.vim - plug.vim -> plugins.d/main.vim Signed-off-by: Nanda Lopes <nandalopes@gmail.com>
Last time I tried a similar migration (to NeoBundle, back in 2013), @skwp brought up some reasons / conditions not to do this. So I'll defer to him to address this new attempt 😇 . I like vim-plug a lot and it's what I've been using in my own fork for some years now as well |
I've tested and passed:
I've managed to copy |
Hi folks, have been a happy user of this repo for many years. This is a nice change. Just wondering - do the utilites and docs mentioned in https://github.com/skwp/dotfiles/blob/master/doc/vim/manage_plugins.md need to be changed too? |
No need to change the docs. I've managed the utilities to use the same aliases, but changing internal implementation. |
This PR changes vim plugin manager from
Vundle
tovim-plug
.Close #864