All,
I'm curious to know peoples' opinions on this matter, especially Bram,
since he's back.
The issue is about whether the completion popup menu should disappear
when the user hits backspace all the way back to the initial
pre-completed state. Right now, the popup window disappears.
--Matt
On Mon, May 15, 2006 at 12:00:26AM +0200, Martin Stubenschrott wrote:
> On Sun, May 14, 2006 at 05:24:35PM -0400, [EMAIL PROTECTED] wrote:
> > All,
> >
> > If I hit <c-n> on an empty line to do keyword completion ('completeopt'
> > is set to "longest,menuone"), and I type a few chars, then hit backspace
> > all the way up to the beginning of the line; the popup window at that
> > point disappears. The behavior used to be that the popup window would
> > stay up. I think it's inappropriate to have the popup window disappear
> > just because you arrived at the initial state when the popup window
> > appeared. Couldn't the behavior be that the popup window disappears when
> > you go yet passed this point?
>
> I also agree with your point.
>
> Often after pressing <c-x><c-o> to do context senstitive completion, I
> press one character to narrow things down.
>
> When I then see, that the narrowed matches don't make sense, I want to
> press backspace to get all the previous machtes back.
>
> E.g. often I don't know if it's .length() or .size() to get the length
> of an array. Then I press array.<c-x><c.o> and a 'l' - if this
> doesn't show me a .length() parameter, pressing <bs>s<c-n> to complete
> .size() would make sense.
>
> --
> Martin
