On Tue, May 16, 2006 at 08:57:57AM -0400, Benji Fisher wrote:
On Tue, May 16, 2006 at 04:06:27PM +0800, Linsong wrote:
Hi, all
I encounter a strange problem when use vim7, the following steps
will reproduce the problem:
1. run vim with command: vim -u NONE -U NONE
2. set the follwoing options:
:set nocompatible
:set completeopt+=longest
3. input some text into the buffer like this:
foo.bar bet better
4. then input foC-P, fo will completed as foo, that is expected,
input '.b' after foo, now the text becomes foo.b, then press
C-P, it will become fo.
Is it expected or maybe a bug? Any explanation is welcomed!
Best regards,
Vincent
I can confirm this. It looks like a bug to me. I have run into
similar problems before, but have not figured out how to reproduce them.
Thanks for the reproducible example.
HTH --Benji Fisher
I can confirm the same as well. Probably a bug. Difficult to catch
because normally people get out of completion mode. If, at foo.b, one
presses c-e to exit from completion mode, the following c-p will
work appropriately.
--Matt
