How to use this plugin on Github where keyboard events are stealed.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
I used to Search with / and pressing N to find the next occurence in code view of github. But now github hijacks and does all sorts of evil things to prevent me from using this Vimium features. pLease Help don't let github win.
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 reproducing the problem in GitHub's code view with Vimium's / search and N next-occurrence commands, comparing behavior with ordinary pages. Trace how Vimium handles keyboard events in that view and define done as restoring those commands without disrupting GitHub's code-view behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100