>> To demonstrate this, start vim like this:
>>
>> vim -N -u NONE --cmd 'autocmd CursorHold * if 0 | endif'
>>
>> In four seconds ('updatetime') the intro message will disappear.
>
> Thanks for your report.
> I also reproduced this problem. This patch may fix it.
> Sorry, the patch I sent last time is wrong formatted. I fix and resend it.
>
>
> On 2013/03/20, at 16:51, Gary Johnson wrote:
>
>> On 2013-03-16, Bram Moolenaar wrote:
>>> Hayaki Saito wrote:
>>>
>>>> Hi, Bram
>>>> I wrote a quick fix patch for this.
>>>> I guess this patch does not fix the fundamental problem.
>>>> In $TERM=3Dansi environment, the incomplete sequence "ESC [" seems to be =
>>>> registered at termcode map.
>>>
>>> Thanks for the fix, I'll include it.
>>>
>>> Hopefully you can think of a way to make this more robust.
>>
>> I discovered another problem with patch 7.3.859: when the
>> CursorHold event is triggered shortly after startup, the intro
>> message disappears.
>>
>> To demonstrate this, start vim like this:
>>
>> vim -N -u NONE --cmd 'autocmd CursorHold * if 0 | endif'
>>
>> In four seconds ('updatetime') the intro message will disappear.
>>
>> The "if 0 | endif" is just a command I chose that would have no
>> effect on the intro message by itself.
>>
>> I noticed this behavior when I updated one of my vim installations
>> from 7.3.646 to the latest, 7.3.874, to test Christian Brabandt's
>> cedit patch. Shortly after starting the new version, the intro
>> message disappeared. I tracked the problem down to the CursorHold
>> autocommand in one of my plugins, but I've been using that plugin
>> for years without this behavior. I then used the hg bisect command
>> to determine the patch that introduced the behavior.
>>
>> $ hg bisect -g
>> The first bad revision is:
>> changeset: 4215:ecf21be84def
>> tag: v7-3-859
>> user: Bram Moolenaar <[email protected]>
>> date: Wed Mar 13 19:29:28 2013 +0100
>> summary: updated for version 7.3.859
>>
>> I looked briefly at the changeset (hg diff -c 4215) but nothing
>> jumped out at me as being the cause.
>>
>> Regards,
>> Gary
>>
>> --
>> --
>> You received this message from the "vim_dev" 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
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "vim_dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
> <fix_cursorhold_behavior.diff>--
> --
> You received this message from the "vim_dev" 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
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
fix_cursorhold_behavior.diff
Description: Binary data
-- -- You received this message from the "vim_dev" 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
