kura
Forked Due to Apparent Loss of Maintainer
The maintainer of this repo appears to have vanished (I tried to e-mail him but his domain has expired). Maintenance has now been taken over by brbsix in the fork at brbsix/vagrant-bash-completion, with all PRs as of this date incorporated.
(The previous fork at c-j-s/vagrant-bash-completion has been removed.)
Argh. Would have been nice if you'd announced this here before I'd spent an hour forking and pulling in all the other changes and the like. This issue is, of course, this repo is the top hit for "vagrant bash completion" on both Google and DuckDuckGo, soltysh and ddarbyson come in on the top page of each respectively and you don't appear at all, unfortunately. And keep in mind that forks don't appear in github searches either.
Anyway, now that people know about this, do you want to pull in to your repo the changes I have that you don't (box prune and the cygwin/mingw fix, from the looks of it) and then I can kill my fork?
Apologies. I suppose it's not particularly convenient to find, but doesn't my fork show up at the top of https://github.com/kura/vagrant-bash-completion/network?
I just added box prune support in https://github.com/brbsix/vagrant-bash-completion/commit/d6f10f0413eb03ecccb364cee5c67575a340935c (I had already implemented it a while ago but didn't commit until now). https://github.com/brbsix/vagrant-bash-completion/commit/9666a8acb009977baa8d21a5253f5f71b34b6506 should address the cygwin/mingw issue.
Ah, that's a good (if not obvious) way of searching. Anyway, good stuff. I've just updated and done a quick test of the current head of your master branch and everything seems ok. So I'll use that from this point on and kill my own fork. Thanks for the quick response!
@c-j-s https://github.com/c-j-s/vagrant-bash-completion throws 404 Page not found
@yermulnik: Right, as one might expect if one reads the message immediately above yours. :-) But good point; I've edited the initial message in this thread to point directly to @brbsix's repo.