AnkiWeb
- Rating
- 6 (👍 6 · 👎 0)
- Updated
- 2021-09-04
- Anki versions
- 2.1.35~
- Description language
- en
AnkiWeb addon 981580052
Scrolls the Anki reviewer with vi/vim-like j and k keys, with configurable scroll amounts and shift-J/K mappings for page up/down.
Open on AnkiWeb GitHub Ask about alternatives
abandoned
| Min Anki | Max Anki | Updated |
|---|---|---|
| 2.1.35 | + | 2021-09-04 |
Loading…
Allows scrolling in Anki's reviewer with vi/vim-like keys j and k, plus e and d for page scrolling.
Maps arrow keys to Again, Hard, Good/Show Answer, and Easy, adds customizable smooth Shift-scrolling, context-aware safety checks, and a visual settings dashboard.
Enables keyboard-driven Anki reviewing with hjkl grading, flexible front-side rating, hidden answer buttons, Pass-Fail mode, zoom shortcuts, and color-coded grades.
Configurable mouse and trackpad hotkeys navigate Anki review, overview, and congratulations screens, with middle-click drag scrolling and deck browser access.
Enables vi/vim-like j and k scrolling in the Anki reviewer for Anki24+, with an options UI and customizable shortcut keys.
Controls Anki reviews hands-free using customizable head and hand gestures for answering, scrolling, and other actions, with calibration, sensitivity, shortcuts, and camera preview.
Scroll in reviewer with vi/vim keys j and k
If you type in your cards and the backside of cards in the deck is huge then you often find yourself reaching for page up/page down/arrow keys to scroll down. Since I am a vim user it was really frustrating not having jk to scroll considering they are not even mapped to anything by default. This usecase might be rare, but it was so refreshing finally not having to move hands to just scroll for every card.
You can configure the amount of scroll in a config. Also notice that there are additional mappings for J and K (shift+j, shift+k), so that you can use them as page up/page down, though there was no way to do an actual page-vise scrolling, because qtwebengine does not support that javascript function, but within a few minutes of tweaking you should be able to find the right value.
I have not tested this on earlier versions, but I think this should work just fine even before 2.1.35. Tell me if it is broken on earlier versions and I will look into it