Entirely off-topic, but...
The first thread I see on the vim_mac mailing list is started by a guy in my
own neighborhood. Crazy serendipity.
Threv
--
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
On Jul 10, 2011, at 4:25 PM, David Patrick Henderson wrote:
If it's not a vimball, then you need to make it one before you can use
VimBall features using MkVimBall. My method follows:
Thanks for the explanation, David. I'm torn at the moment between the the
apparent simplicity of the
On Jul 11, 2011, at 4:42 AM, Andrew Stewart wrote:
I tried VimBalls a while ago but grew frustrated at the work that needs doing
when a script/plugin isn't already packaged as a VimBall. I switched to
Pathogen and it has always worked wonderfully. If a conflict with
VimOutliner is the
In Section 12 of the documentation for VAM there is this:
You have to trust script authors:
Because everybody can upload everything to the repositories (in particular
www.vim.org) you must trust authors. I can't review all code - so expect code
to steal your passwords, run sudo rm -fr / ... etc.
On 9 Jul 2011, at 18:17, Eric Weir wrote:
I now have a few Vim plugins installed. I assume there will be more, if not
many more, coming down the path. Back when I was just getting started with
Vim a couple months or so ago I had a brief flirtation with Pathogen. Thought
I would get set up
On Jul 9, 2011, at 7:52 PM, David Patrick Henderson wrote:
A vimball is really just all the add-on files concatenated together +
information about where the files are stored within the hierarchy of either
the user’s .vim or the system wide location.
I've read the help on vimball, David.
On Jul 9, 2011, at 4:14 PM, David Patrick Henderson wrote:
No experience with either pathogen or an add-on manager, my method is to use
vimballs. I turn all of the vim add-ons into vimballs before installing them
which makes managing my plugins fairly painless.
Thanks, David. I thought
On Jul 9, 2011, at 7:52 PM, David Patrick Henderson wrote:
It is superficially a means of packaging. A vimball package distributes the
add-on files to the correct directories and runs tags on the add-oh docs if
it has any. A vimball is really just all the add-on files concatenated
