Bram and Aaron,
Bram wrote:
> > I'm still finding the ^P/^N behaviour in insert mode kind of annoying.
> > I just did something like this:
> > - Edit a file with the text "numMatches" in it.
> > - Type "numMb" and hit ^P.
> > - It's a typo so no matches come up. In the meantime vim starts
> > madly searching through header files in the background.
> > - Hit <BS>, then "a" to give the text "numMa".
> > - Now it should find the right match. Vim still seems to be
> > searching in the background. Is it supposed to find the correct
> > match now straight away? It doesn't. Or is it up to me to hit
> > ^P again?
> > - If I hit ^P again, nothing happens. I can repeatedly hit it and
> > no matches are found and no menu appears (note: all this is
> > still while vim is searching in the background). In 6.3 this
> > would have given me the right match.
> > - So instead I try ^N. Now a menu appears with my original text
> > ("numMa") and the match I want ("numMatches"), but no matter how
> > many times I hit ^N it just stays stuck on the first item which
> > was my original text! It's stuck again in a similar way to what
> > I described in another email.
> >
> > What is supposed to happen when you hit <BS> then hit another letter
> > during completion mode?
>
> What version are you using? I fixed a problem with <BS> just before
> sending out Vim 7.
Yes, you did fix something, but the description above is what I saw in
the final 7.0 release.
Aaron wrote:
> > I still think ^N/^P should wrap around the matches found so far
> > while vim is searching in the background.
>
> This is not a new feature in vim7. This has been in the codebase
> for a while.
Previously searching in the background only began after using ^N/^P
enough times that all matches from the current file (and other open
buffers) had already been found. ^N/^P would work as you might expect
until then. You could ^N to get the following match, then ^P a couple
of times to get the previous match. Now this doesn't work while the
background searching is going on.
Would still really like an option to turn off the display of file
names that race past during the background search too. The only
reason for seeing this kind of thing is when it happens in the
foreground, so that you know vim is busy but making progress and soon
you'll be able to type again. When it happens in the background it's
not holding you up, and should keep what it's doing to itself. It's
good that it happens in the background, it's not so good that it tells
you about it in the foreground. Your eyes are automatically drawn to
areas where things are changing, but it's an unnecessary distraction.
Thanks,
Rob.
--
Robert Webb <[EMAIL PROTECTED]>,
Want to make polyhedra?
http://www.software3d.com/Stella.html
