Igor Prischepoff wrote: > Hi, i think i have found a bug in vim 7.0 > Patch level 1-109. > Windows version +perl +python (i don't think this matters in this case) > > here is how to reproduce: > gvim -u NONE -U NONE > :set complete-=t " don't want complete from tags file - it's not > important, just to switch off message > :set complete+=longest " that's important
You must mean 'completeopt' here. > i "now we in insert mode > > one two > o<C-N>:t<C-N>"now trying to complete second time - no completion, nothing" > i.e. i've got resulting text in buffer like this: > > one two > one:t > > and no 'two' on second C-N when trying to complete 'two' and message "Back > at original" > > (First completion works as expected, but second didn't shown and not > complete at all) > if remove 'longest' from 'complete' then everything works as expected. > > Can you reproduce that bug? > Or it's intended behaviour? Vim is still in completion mode and there is no word matching "one:t" thus you don't get any completions. If you type CTRL-N one more time then it works. I can see this is unexpected, perhaps when "longest" is used and there is only one match it should work as if that match was selected with CTRL-N. -- hundred-and-one symptoms of being an internet addict: 4. Your eyeglasses have a web site burned in on them. /// Bram Moolenaar -- [EMAIL PROTECTED] -- 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://ICCF-Holland.org ///
