Vimium: unable to unset ']' key

[Akenaide]

Hello,
browser : Chrome

I can not unset ] key. I don't even know what is exactly do, I just see it unfocus when I typing.

I add "unset ]" in the config but I don't see any change.

Great plugin I starting using vim a lot and it feel great to use the same way to navigate in my browser.

sorry for my poor english

[slavaGanzin]

]] move you to 'next page'
you must be in insert mode (focused on input) to prevent any normal mode vim-like behaviours

[Akenaide]

Yeah I seen the ']]' map but I type only ']'.

Well, i don't understand my issue is specially when I'm focused on input. When I'm want typing something like " [Yay]" I lose focus with " ] " and the result is "[Yay ".

[slavaGanzin]

I can't reproduce this. Maybe show the site and input where you get this

[Akenaide]

Github and reddit in the search bar

[slavaGanzin]

I try on all three search boxes and successfully print '[yay]'. So it isn't vimium bug

[mrmr1993]

This sounds like it could be an international keyboard issue. Does it still happen when Vimium is disabled?

[Akenaide]

Okay, I will search with my another plugin but if I disactivate vimium I do not have my issue anymore.

Thanks for your help !

[Akenaide]

I use french azerty layout, and no when Vimium is disabled it works fine.

EDIT: no when Vimium is disabled it works fine

[L3nn0x]

Hello, I have exactly the same problem.
When I'm writing stuff in my browser (any input and any web page) with vimium activated, I can't write ']'. If I try, the input box loses focus.
I tried without Vimium activated and everything's fine.
I thought it was a mapping problem, but adding "unmap ]" or/and "unmap ]]" doesn't seem to change anything.
I have a french azerty keyboard layout if it's of any help.

Thanks a lot in advance.

[tyrcho]

Same for me exactly, with an Azerty keyboard. It means that on any site where I need to type a closing square bracket, I need to disable Vimium :-(

I've also tried to use unamp like this with no success.

unmap <a-c-[><a-c-[>

Note that the square brackets are actually a combination of AltGr + 5 or ° keys on Azerty.

Here is what the log looks like when I hit jklm[] :

checking keyQueue: [ j ] main.js:643
new KeyQueue:  main.js:645
checking keyQueue: [ k ] main.js:643
new KeyQueue:  main.js:645
checking keyQueue: [ l ] main.js:643
new KeyQueue:  main.js:645
checking keyQueue: [ m ] main.js:643
new KeyQueue:  main.js:645
checking keyQueue: [ <a-c-[> ] main.js:643
new KeyQueue:  main.js:645
checking keyQueue: [ ] ] main.js:643
new KeyQueue:  

[youbicode]

any solution for this partical issue ?

[mrmr1993]

Sorry this has been sat so long. I'd been hoping that a fix for #301 would resolve this along the way, but #1140 didn't make the grade.

I've pushed 956145d as my attempt at a (very low quality) fix. @niwox (or somebody else), could you test it? If it works, I'll put it in a PR.

[Akenaide]

Sorry for the late, your change do the job. I can type "]" again with vimium activate o/

Thanks

[Akenaide]

oops

[youbicode]

No fix on the official release yet for this issue ?

[roessland]

I cannot type [ in Vimium on my Norwegian keyboard (I had to copy paste it in here). It is typed by pressing AltGr+8, or equivalently Ctrl+Alt+8. I lose focus from the textarea when I press it.

It's also impossible to unmap. I've tried

unmap [  
unmap <c-a-8>  
unmap <c-[>

and some other combinations.

[zieren]

Same here (German layout, Windows 7 x64).

[smblott-github]

OK. Added _next-version_ label. We should fix this.

(It happens because Ctrl-[ is hardwired to be "Escape".)

[youbicode]

I believe Alt Gr - [ is hardwired to be Escape too. Any fix for that ?

[andersoyvind]

This will be a noticable issue, as users of online javascript editors (jsbin, jsfiddle etc) or the interactive training sites (codeschool etc) will face the -issue, eventually.
Glad that it is worked on.

[colin-kiegel]

this is really a strong pain point on non-US keyboards
please consider this fix: https://github.com/philc/vimium/pull/2215

[smblott-github]

Closing. #2215 is merged (and released), which should fix most of the issues here.