On 2014-01-14, Ben Fritz wrote: > On Tuesday, January 14, 2014 11:23:53 AM UTC-6, parcs wrote: > > 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. > > > > But with that method, whether on a local PC or over SSH, if there > are a lot of LARGE buffers so that scanning for keywords takes a > long time, the user will have no indication whether Vim is > actually working on something or has stopped responding. > > Personally I'd rather wait for 2 seconds knowing that Vim is > actively processing multiple files, than wonder after 30 seconds > whether Vim is almost done or whether I should just kill it with > <C-C> and type stuff manually.
I'll second that. My only experience with slow keyword completion was on a development system where vim was running locally but all the source files were on a remote file system. The slow updates of the "Scanning" messages and the names of the files being scanned was my clue to the cause of the problem. 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.
