[FF] Unable to use custom navigation key mappings in Visual mode
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
I shifted my navigation keys to one key right (j,k,l,ş instead of h,j,k,l) with this configuration:
unmap h
map j scrollLeft
map k scrollDown
map l scrollUp
map ş scrollRight
unmap H
map J goBack
map K previousTab
map L nextTab
map Ş goForward
However when I enter Visual mode by pressing 'v', navigation keys revert to their original bindings (h,j,k,l). Is this a bug or am I missing something obvious in my configuration?
Steps to reproduce:
- map scrollLeft, scrollDown, scrollUp and scrollRight commands to j, k, l and ş keys respectively like in the configuration above.(use whatever key you have next to 'l' instead of 'ş' in your keyboard)
- Enter Visual mode.
- Try using your newly mapped keys.
Browser: Firefox 57.0.1 64-bit
OS: Ubuntu 17.10 64-bit
Vimium version: Vimium 1.62
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Reproduce the custom j, k, l and adjacent-key mappings in Firefox, then enter Visual mode and compare the active bindings with normal mode. Done means the configured navigation keys work in Visual mode without reverting to h, j, k and l.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100