Re: completion exit
> > Maybe it would be a good idea to have an option like 'completepast' orIs that the only argument you have against it?
> > 'completetypeover' so that someone can do ":set nocompletepast" and have
> > the completion mode end when you're typing past any items in the menu.
> > What I mean is, you have these entries after func<c-x><c-o>:
> > funcGood
> > funcGoodStuff
> > funcGoodnotsogood
> > and so it completes up to "funcGood" and you just type "(3, 4);", as the
> > arguments for that function.
> > With the 'nocompletepast', completion mode would stop as soon as you
> > open the parenthesis. Currently vim doesn't escape completion mode, and
> > hitting backspace a few times will bring up the menu again.
> It doesn't make much sense to have an on/off option for this.
>Another idea I was thinking is a 'completionchars' option to specify
> Note that typing a space already quits completion mode, and often that's
> It would also possible to stop completion when you type a non-letter.
> But that means when you accidentally hit the wrong key, or in your
> text some non-letter characters can be in the completed text, you quit
> completion too early. For C code the "(" is part of the completion, I
> can imagine for some languages the first argument follows.
which characters exit the completion.
You would do ":set completionchars+=(" ... or actually, the completion
plugin might do that. Then '(' would exit just like a space does.
Is that better?