Excerpts from Tom Link's message of Mon Mar 21 19:44:55 +0100 2011: > External programs like: wget, unzip, tar, gzip > Perl/python/ruby packages/libraries etc. A perl/python/ruby-based > solution usually isn't that easy to use for somebody who doesn't use > that language for development and hence doesn't know how to install > this or that library. So this would mean authors must add a description how to use easyinstall/ gem/ or other commands. > > What do you mean by "integration"? > It's probably synonymous to "written in vimscript and can be invoked I expect most Vim users to know how to write a custom command / mapping. So this does not really matter.
You can script VAM using -c or --cmd. See the test .sh file top level directory. (Yes - it may suck and maybe breaks eg error reporting and that) Should the core (manipulating paths, eg run git pull) be separated from manipulating runtimepath? Than having two user interfaces (Vim and command line) would be possible. Marc Weber -- You received this message from the "vim_use" 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
