On 11/02/09 06:42, Tom Link wrote:
>> You can specify the base path with the final arg to MkVimball.
>
> If you wanted to create vimballs from cygwin bash by calling Windows
> gvim (you could of course use cygwin's vim but ...), you'd have to
> convert the path which works most of the time but can be cumbersome.
> But thanks for reminding me of that extra argument.
>
> Regards,
> Thomas.
IMHO it makes sense to have a non-GUI version of Vim-for-Cygwin and use
that under Cygwin bash in preference to native-Windows versions. Or, if
your Cygwin Vim is too outdated, you can run native-Windows Vim at the
cmd.exe command line. In both cases, I believe (but didn't check) that
you could use (for instance, and with the extra argument)
vim -u NORC -N -es -c 'MkVimball filelist $VIM/vimfiles' -cq
if you didn't want to bother with an interactive Vim session.
Best regards,
Tony.
--
BRIDGEKEEPER: What is your favorite colour?
GAWAIN: Blue ... No yelloooooww!
"Monty Python and the Holy Grail" PYTHON (MONTY)
PICTURES LTD
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
