Re: Completion very slow
- Hi Bram
I am interested in completion... Thah is, it really doesn't solve the
problem that I can type while it searches. In my opinion the lazy
approach is much more usable. Maybe one could optimize the Vim 7.0
approach so it only searches for the next/previous 5 matches.
Amir -- http://amix.dk/
On 3/30/06, Bram Moolenaar <Bram@...> wrote:
> Amir Salihefendic wrote:
> > I just checked the ftplugin files in my Vim 6.4 build and both include
> > and includeexpr are set.
> > I also just compared the two completions (In Vim 6.4 and Vim 7.0). The
> > 7.0 version is a lot slower than Vim 6.4 (using same vimrc, same
> > plugins and same open files).
> > The problem with Vim 7.0 seems to be that it isn't lazy. It seems that
> > when one types "g" and hits <c-n> it finds all the matches. While Vim
> > 6.4 doesn't.
> > My conclusion is based upon that Vim 6.4 only displays "match 1",
> > while Vim 7.0 "match 1 out of 70".
> That is right, Vim 7 continues to find matches, so that the popup menu
> can be filled. But you don't have to wait for it to finish, you can
> type something while it's still busy.
> To the optimist, the glass is half full.
> To the pessimist, the glass is half empty.
> To the engineer, the glass is twice as big as it needs to be.
> /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
> /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\ download, build and distribute -- http://www.A-A-P.org ///
> \\\ help me help AIDS victims -- http://www.ICCF.nl ///