On 12/09/12 01:54, Timothy Madden wrote:
> 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
>
Yes, in batch mode (with -es) no scripts are sourced. To source them
anyway, add on top of your build.vim
if filereadable("$HOME/.vimrc")
source ~/.vimrc
elseif filereadable("$HOME/_vimrc")
source ~/_vimrc
endif
runtime! plugin/*.vim
Best regards,
Tony.
--
ARTHUR: Be quiet!
DENNIS: Well you can't expect to wield supreme executive power just 'cause
some watery tart threw a sword at you!
ARTHUR: Shut up!
DENNIS: I mean, if I went around sayin' I was an empereror just because
some
moistened bint had lobbed a scimitar at me they'd put me away!
The Quest for the Holy Grail (Monty
Python)
--
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
Wednesday, September 12, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment