Great work on Waldo. I'm running into a bit of a problem when managing plugin installation via the excellent Vundle vim plugin manager, which supports two source types:
Git/Github repos that use a Pathogen-style plugin structure
In this case, Vundle can't manage Waldo.vim because it can't find it via either of the above two methods. It's great that Waldo.app automatically puts Waldo.vim in bundle/Waldo/plugin/Waldo.vim, but that doesn't help much when trying to use Vundle to manage plugins since it throws an error when going through its plugin update process.
I can think of two potential solutions:
In Github master, move Waldo.vim into a folder called plugin in order to match the plugin layout that Pathogen/Vundle expects.
Of course, the two are not mutually exclusive. The advantage to the latter Vim Scripts method is that only the Waldo.vim script would be installed instead of the whole Waldo repository source (Xcode project, etc).
What do you think? Looking forward to your thoughts!
Great work on Waldo. I'm running into a bit of a problem when managing plugin installation via the excellent Vundle vim plugin manager, which supports two source types:
In this case, Vundle can't manage Waldo.vim because it can't find it via either of the above two methods. It's great that Waldo.app automatically puts Waldo.vim in
bundle/Waldo/plugin/Waldo.vim
, but that doesn't help much when trying to use Vundle to manage plugins since it throws an error when going through its plugin update process.I can think of two potential solutions:
Waldo.vim
into a folder calledplugin
in order to match the plugin layout that Pathogen/Vundle expects.Waldo.vim
to Vim ScriptsOf course, the two are not mutually exclusive. The advantage to the latter Vim Scripts method is that only the
Waldo.vim
script would be installed instead of the whole Waldo repository source (Xcode project, etc).What do you think? Looking forward to your thoughts!