> It looks like someone has changed the logic of the longest match in vim > autocompletion. Now it tries to do the longest match after each new > letter entered. And there are some ugly bugs which causes it to > segfault the vim. Not mentioning that it's also very slow now. Looks > like it calls omnifunc with every character entered. > > Probably this commit causes the problem: > http://code.google.com/p/vim/source/detail?r=44ffd0a8abcdba441216514cb711649eb1169876
Yes, the motivation behind this patch looks somewhat counter-intuitive (http://groups.google.com/group/vim_dev/browse_thread/thread/86643b0112664dfe) Why on Earth a completion of "a" would be "foo1", "foo2", "foo3" but "bar1", "bar2", "bar3" for "ab"? If there really is a reason to behave like that we'd better to implement this somehow else. E.g., the completion function could return an extra value which says that the function wants to be invoked every time a user types a letter. -- Sergey Khorev http://sites.google.com/site/khorser Can anybody think of a good tagline I can steal? -- 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
