Re: sourcing functions in file with has gui_running from .vimrc

On 04/11/12 19:00, Chris Lott wrote:
> On Sun, Nov 4, 2012 at 7:56 AM, Tony Mechelynck
>>
>> If these options are set correctly and you still don't see the tabs, then
>> another possibility is that Vim would set 'guitablabel' and 'guitabtooltip'
>> to some default (or empty) value at GUI startup. To counteract this, you can
>> set them at the GUIEnter autocommand event:
>>
>> if has('gui') && has('autocmd') && has('windows')
>> au GUIEnter * set gtl=%{GuiTabLabel()} gtt=%{GuiTabTooltip()}
>> endif
>
> Thanks. It's interesting that, as originally written, if the code was
> in the .vimrc it worked, but if included in a separate file it did not
> unless I use the GUIEnter command...
>
> But it worked! Thanks!
>
> c
> --
> Chris Lott <chris@chrislott.org>
>

A script sourced from your vimrc does the same as it would if it
replaced the :source statement (except that it runs in a different
script context, and anything defined with s: or <SID> in one of the
scripts cannot be accessed from the other).

OTOH, autocommands for the GUIEnter event are run at the end of
initialization, after opening the GUI but before the VimEnter event, and
of course not when running in Console mode.

Check your vimrc for overriding the other file's 'guitablabel' and
'guitabtooltip' settings after the :source statement. In cases such as
this, the last one wins. Since the GUIEnter event is near the end of
initialization, it overrides anything that is done at startup without an
autocommand.


Best regards,
Tony.
--
If the weather is extremely bad, church attendance will be down. If
the weather is extremely good, church attendance will be down. If the
bulletin covers are in short supply, however, church attendance will
exceed all expectations.
-- Reverend Chichester

--
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