[Vimperator] unmap bug

[Aaron Bohannon]

OK.  I was somewhat incorrect.  The precise behavior is this: The
first time you type ":map X Y" or ":unmap X" _after_ typing ":map"
(with no args), your cursor will be left at the command line.  This
almost sounds too weird to make sense, but to give an example
precisely, you can type

:map J gt<ENTER>
:map<ENTER>
<ENTER>
:unmap J<ENTER>

and you will still be in command-line mode with the cursor after the
J.  (The <ENTER> on the third line is in response to "Press ENTER or
type a command to continue" and you will get the same buggy behavior
if you omit it and immediately start typing the fourth line.)

I thought this bug related to "unmap" since I had always checked my
mappings with ":map" before trying to unmap one of the them. :)

-Aaron

On 10/24/07, Martin Stubenschrott <stubenschrott at gmx.net> wrote:
> On Tue, Oct 23, 2007 at 01:03:03PM -0400, Aaron Bohannon wrote:
> > When I type ":unmap foo" and hit ENTER, I am not returned to normal
> > mode, but rather my cursor is left in the command line, and the string
> > ":unmap foo" is also left in the command line.  This is a bug, right?
> > This behavior seems to be consistent.  I also noticed it at least once
> > when using ":map" to create a binding, but have not been able to
> > duplicate it in that case.
>
> It's intentional that ":unmap foo" remains in the statusline after
> pressing enter, just like vim.
>
> However, I _am_ put back to normal mode, and can continue to work from
> there. Maybe also a focus issue?
>
> Can you give the exact commands to reproduce?
>
> --
> Martin
> _______________________________________________
> Vimperator mailing list
> Vimperator at mozdev.org
> http://www.mozdev.org/mailman/listinfo/vimperator
>