On Thu, 13 Jul 2006 at 1:15pm, Maciej Kalisiak wrote: > On 13/07/06, Hari Krishna Dara <[EMAIL PROTECTED]> wrote: > > You are probably talking about the insert-mode completion rather than > > the omni-completion. Omni completion is meant is similar to the MS > > intellisense, and is not turned on by default. > > Ahhh, I see, yes, I think you're right. > > But is there some option which causes it to trigger *automatically*? > Sometimes as I'm midway through typing in a function name or > identifier the popup comes up automatically, without me having pressed > ^N... that's one of the most annoying parts.
I am not aware of anything that can do this. Which language are you using? Take a look at the ftplugins for the language and see if it is doing anything specific to completion. > > > In contrast, the insert-mode completion is on by > > default, and gets triggered when you use ^N, ^P etc. in insert mode. > > Also, this completion doesn't use your 'path' but by default your tags > > setting, and all the loaded buffers etc. > > Hmm, I noticed the huge performance hit when I extended my path > variable, without having touched my tags, but perhaps Vim in the > background regenerates my tags *based on* my path variable, meaning > it's producing a much larger tags file now... As far as I know, Vim doesn't generate tags file, except for the help documentation. However, I noticed the "i" and "d" options in 'complete' setting which say that Vim scans for all the included files. I don't know if the files are looked up in the 'path' setting, but you might having this issue (check if you have these values in 'complete'. > > > This can be customized by using > > the 'complete' option (e.g., you can completely avoid looking into the > > tags files). It is possible that you recently added more tags files > > which is causing this delay in completion. Actually, without any change > > in tags files, I also saw a difference in performance of the insert-mode > > completion in Vim7 compared to Vim6.3, and not sure if disabling the > > menu will make any difference. You might want to check removing "menu" > > and "menuone" from 'completeopt' will make any difference (this should > > disable popup menu). > > Well, doing 'set completeopt=' (i.e., set it to nothing; previously it > was set to 'preview,menu') seems to speed things up significantly, > although it is still not lightning fast as before. But we're talking > here a difference of going from 10s to 1s wait times! The 1s wait is > almost acceptable now. Good to know this. > > > Since you mentioned that you find the :find command very useful, might I > > put in a plug for my lookupfile.vim plugin? When you use LUPath command, > > it cleverly takes advantage of the Vim7 completion menu (which works > > even when you disable it in 'completeopt') to lookup matching files as > > you type in a partial filename. You can download it from: > > > > http://www.vim.org//script.php?script_id=1581 > > Thanks! I'll check it out, it sounds very interesting. And please send me your feedback, and don't forget to rate it, if you like it. -- Thanks, Hari __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
