On Friday, January 27, 2012 2:37:37 AM UTC+1, Dave H wrote:
> On 26 Jan 2012, at 14:20, David Sanson wrote:
> About installing plugins: vimballs seem to work well enough, and don't require futzing around in netrw. Anyone have any tips for creating vimballs from plugins when using Pathogen? I'd like to be able to create vimballs of my favorite (non-python or ruby dependent) plugins on my laptop, and then transfer them over to my iPad. But MkVimball seems to choke on me because the files are in ~/.vim/bundle/pluginname instead of ~/.vim.
> Creating MkVimball doesn’t care about the directory what it does care about is that the paths to the files are correct. I make vimballs from all the plugins I use as it makes it easier to manage them. I usually create them from within the unzipped folder. It was slightly non-obvious to me the first time I attempted to create a vimball from a zipped archive. The trick it turned out was to list each file on a separate line with either full or relative path to the directory to which your vimball will get made; then, highlight all the lines and do :MkVimball vimball_name /path/to/vimball. Hope this helps.
> David P Henderson
> c: xxx.xxx.xxxx
> "Beautiful bodies and beautiful personalities rarely go together."
> -- Carl Jung
This version, without Ctrl key touch, and other bugs, is a useless Vi not iMproved!
You received this message from the "vim_mac" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
You received this message because you are subscribed to the Google Groups "vim_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_mac+unsubscribe@...
For more options, visit https://groups.google.com/groups/opt_out.