Cameron Eagans

@justinmk I don't want to design a package format. I just don't want to crawl Github. It's simple enough to login with Github and essentially say "my repo is a...

@Shougo @tyru IMO, that's way too complicated. There's really no reason for all of that complexity if you look at what the requirements actually are: 1. We want a list...

> the idea sounds Vim plugin developers must specify the Web hooks URLs from GitHub or BitBucket site's "Settings" page. You'd log into the package index with your Github or...

Coming back to this: I don't think we need to create a registry now. Github does a lot of the heaving lifting for us. That is, we don't need a...

Fortunately, we don't only have to choose one :) I don't disagree that installing a plugin manager with a single command would be awesome, but that's not really something that...

Extremely likely that `patch` is not installed. You can verify with `composer -vvv install`

Yep. https://github.com/cweagans/composer-patches/issues/400 :)

This doesn't seem like a composer patches bug. If composer doesn't call the methods this plugin defines, there's not much we can do..

These ones: https://github.com/cweagans/composer-patches/blob/1.x/src/Patches.php#L71-L82 I think the solution here is to just not run composer with `--no-scripts`, tbh.

Usually, `composer update your/package` (for whatever thing you patched). Usually, `composer install your/package` will cause it to be removed and patched as well, but there's some funky behavior in some...