On 09/11/2012 05:37 PM, Tony Mechelynck wrote:
[...]
> That build script consists only of ex-commands, so you can omit the
> leading colons and run Vim in batch mode as follows:
>
> vim -esS build.vim
>
> see
> :help -e
> :help -s-ex
> :help -S
>
> If you want your vimrc to be used, you will need to explicitly add a -u
> argument for it.
>
> You don't need a GUI, so no need to use gvim. If you don't _have_ a
> Console Vim (and are on Windows), well, I don't know if you can avoid
> opening the GUI. But you can try replacing vim by gvim in the above
> command.
I tried with vim instead of gvim and with the -esS build.vim arguments.
While it is true I no longer get the window, now vim exits with the
return code 2 and I get no vimball built.
I suspect vim no longer loads plugins with the above switches, so my
%MkVimball vcscommand-repack
command no longer works.ā
Thank you,
Timothy Madden
--
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
Tuesday, September 11, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment