Patric wrote:
> I noticed that in sessions with many (100+) small buffers, keyword
> completion over a slow network causes a 2+ second hiccup. I think
> this is because during keyword completion, Vim prints the line
> "Scanning %s" for each open buffer into the command line. When
> buffers are small (and therefore keyword scanning is very fast), these
> screen updates happen very quickly one after another and create a
> spike in network traffic which causes the underlying SSH session to be
> unresponsive until all screen updates are accounted for.
>
> I wonder if instead of printing "Scanning %s" for each buffer in the
> session during keyword completion, Vim could instead print say
> "Scanning buffers." just once. This would reduce the amount of screen
> updates performed during keyword completion, thereby making keyword
> completion more responsive under slow terminals/networks.
>
> Here's a candidate patch that implements the above suggestion.
What's done with :vimgrep is that Vim prints a message every second, so
that the user knows it's still busy. That avoids printing a lot of text
you can't read anyway, and still remains informative.
See quickfix.c, around line 3260.
--
You're as much use as a condom machine at the Vatican.
-- Rimmer to Holly in Red Dwarf 'Queeg'
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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.
