Feature: Allow escaping passNextKey mode
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Many extensions provide their own shortcuts.
Using insert mode in websites which contain multiple frames/embeds prevents other extensions from capturing the key and also in case a secondary frame is focued (i.e embedded video) insert mode will apply to it only, preventing hotkeys on the main frame.
The solution I found:
map <c-]> passNextKey
then, when using:
[count]<c-]>
that allows me to work for the next [count] key presses with other extensions's shortcuts.
Problem is - I cannot escape back to normal mode without exhausing the count.
Please consider adding an escape option while in PassNextKey mode.
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; locate the passNextKey mode and its keyboard-handling entry point first. Trace how the count is consumed, then define and implement an escape path back to normal mode and verify that the existing count-based behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100