[implementations-list] [Vimpulse] Bug: Ctrl-n doesn't work as it should

[Alessandro Piras]

I understand what you mean, but Vimpulse has evolved following the
philosophy "let's mimic vim all the way if possible".
I think the problem about dabbrev-expand is in which order it presents the
candidates for completion. dabbrev-expand actually does wrap around, or it
appears to do - I just removed vimpulse-abbrev-expand-after and replaced it
with dabbrev-expand.
I think the idea about vimpulse-dabbrev-expand is searching for the
completion _after_ the cursor, which is ok - that's vim behavior i guess -
but it stops at eof, so when writing some code from scratch is totally
useless - there's nothing after the cursor.

It's not desirable in all cases maybe, but it is in this case, and I'd say
it's desirable unless that vim feature can actually be considered a bug, or
it stays in the way of some big improvement over vim or some kind of extra
good.
Alessandro Piras


On 13 April 2010 18:22, Štěpán Němec <stepnem at gmail.com> wrote:

> On Tue, Apr 13, 2010 at 04:58:14PM +0100, Alessandro Piras wrote:
> > example:
> > ---------
> > giangianni
> > giang<C-n>
> > ~
> > ---------
> > doesn't complete giang to giangianni. It works in Vim.
> > vimpulse-abbrev-expand-after is broken.
>
> Yeah... this is just one of many things that involve some kind of
> thinking about Vimpulse's "philosophy", i.e.: does it make sense to ape
> Vim features into all details? My answer is "no", because it's
> definitely not possible in all cases. And it's not even *desirable* in
> all cases. But that's a matter of opinion, of course.
>
> To be specific: `vimpulse-abbrev-expand-after' is implemented using
> `abbrev-expand', which, unlike Vim, does not seem to wrap around the end
> of buffer when no match is found. Maybe it can be fixed, I don't
> know. But I don't really care either -- my answer is: just use <C-P>
> (C-p).
>
> YMMV
>
>  Štěpán
>
> _______________________________________________
> implementations-list mailing list
> implementations-list at lists.ourproject.org
> https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
>