Skip to content
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

Add option to not remove directories in bundle #31

Open
jtheoof opened this issue Nov 28, 2011 · 2 comments
Open

Add option to not remove directories in bundle #31

jtheoof opened this issue Nov 28, 2011 · 2 comments

Comments

@jtheoof
Copy link

jtheoof commented Nov 28, 2011

This program is great. But the problem is that everytime you run it, even with -n option, it removes directories not bundled in .vimrc.

Unfortunately, I sometimes create custom plugin for work or personal projects. Ex:

.vim/bundles/extra/plugin/work.vim
.vim/bundles/extra/plugin/home.vim

It puts them in .vim/Trashed-Bundles (which by the way should be all lowercase to respect Unix and vim conventions but I'm being picky), which is nice but I have to make an extra

cp .vim/Trashed-Bundles/extra .vim/bundle/

It would be nice to add an extra option like -k --keep-dir to not remove such directories.

@bronson
Copy link
Owner

bronson commented Jan 10, 2012

Check out the 'static' directive:

 If you have directories in ~/.vim/bundle that you'd like vim-update-bundles to ignore, mark them as static.

You're the second person who's asked this, clearly the docs are not getting the job done. If you have any ideas on how I can make that clearer I hope you'll tell me!

And yikes, sorry for the delay. Not sure where the time went. :)

@jtheoof
Copy link
Author

jtheoof commented Jan 10, 2012

Thanks for your reply.

I totally missed that part in the README. You're right it's not very obvious. I personnally believe that it could still be an option when using ./vim-update-bundles but setting them in .vimrc is great too:

" Static: ignore-me

To make it more obvious to new comers, I suggest to include a more complete example in the Description part of the README because most people (like me) don't read manuals all the way down... ;)

Feel free to close the issue if you're not gonna make it an option since the feature is already there, I won't blame you.

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants