On Thu, Nov 14, 2013 at 12:24 AM, Patrick Brisbin <[email protected]> wrote: > Here's a new truly minimal case, which can indeed be triggered with vim > -u example.vim: > > " example.vim > set nocompatible > > function RegenerateCtags() > silent! execute '!true' > endfunction > > autocmd BufEnter * call RegenerateCtags()
I can reproduce the bug using example.vim above, and multiple times in the same terminal window. I can also (sort of) see the ^[[2;2R "flashing by" without example.vim. Here's my "Now you see it, now you don't" scenario: $ cd $HOME $ rm -rf .vim .vimrc # WARNING: You may need adult supervision to do this. $ touch .vimrc $ for i in 1 2 3 4 5; do vi -c q; done # Tada!!! (You should see ^[[2;2R flashing at the bottom left of you terminal) $ rm -f .vimrc $ for i in 1 2 3 4 5; do vi -c q; done # Now it's gone! With an empty .vimrc, "vi -u example.vim" seems to always result in ^[[2;2R nazri -- -- 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.
