Feature Request: Display keys awaiting another input
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
I'm not super familiar with Vim however I do find it slightly confusing that there isn't a particular visual cue that lets me know if Vimium has already primed a key;
If I press g for instance, there's a variety of keys I can press afterwards to have an effect, but there's no distinct way of knowing g was depressed, and I've got to expressly press esc to ensure nothing is registered.
Similarly if I enter find mode; there is no distinction or visual cue showing that I'm still in find mode and awaiting n or N to navigate to other phrase.
I think some visual cues that show what action vimium is currently working on would be really helpful.
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
Start by tracing Vimium's key-sequence handling and find mode to identify where the active state is maintained. Define a visual cue for pending keys and find-mode navigation, then verify that it appears and clears at the expected points without disrupting commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100