Better handling of conflicting plugin names

Issue #5 new
repo owner created an issue

Currently for rtp1/plugin/name.vim and rtp2/plugin/name.vim names will be plugin/name and plugin/name/ which is pretty useless in case somebody need to depend on one of them. I suggest another way now: both plugins are named plugin/name. When it comes to unloading both are unloaded and a warning is shown. When it comes to specifying plugin/name as the dependency frawor should first try to load it from the current runtimepath, then from the runtimepath of one of the other dependencies (subjectable), but only if only one of the conflicted plugins share the runtimepath. If both tries failed then error must be thrown.

Comments (0)

  1. Log in to comment