David Barnett

This should be fixed by #60 (almost ready to submit). I'm changing all the maktaba internal stuff to not touch rtp, so it will only be updated once, by your...

Hmm… I can't reproduce with vim 7.3.429. Followed your directions exactly. What version is your MacVim? You can debug if you do `:func /RegisterPlugin` and then take that function name...

Ah, okay, so this a bug independent of #60 and the register branch. We need working path resolving for all supported vim versions. Let's try to bisect what version of...

Oh, I misunderstood then. Should be fixed on the resolve branch now if you want to double-check I fixed it properly. > I don't know your reasoning behind requiring the...

Nope! We have more projects than contributors so progress is slow. As a workaround, you could add an addon-info.json file to one of hte plugins to give it a different...

Hmm, now that you mention it, generally you won't have conflicting plugins that are both using maktaba, and plugins do assume they'll be able to look up their own plugin...

Yep, but plugin name references from the outside don't help disambiguate, so these implicit strategies might still run into an unavoidable conflict if something looks up the plugin from the...

It looks like the problem is that `maktaba#plugin#GetOrInstall` doesn't call `maktaba#plugin#Detect` first. It tries to install maktaba instead of finding it on rtp, creating a plugin dict for it, and...

Thanks for reporting! I haven't run into it yet but the pointers are wonderful to have tracked for when it does start causing problems in practice.

I just notice the referenced vim bug was closed in 2018. Was it not completely fixed, or just still out there on older vim versions?