4 ms·
I found a different solution to the "getting around the screen" problem: set your keyboard repeat rate to 100 keys/s. Upside: works anywhere, much lighter ment
by CyberShadow 5y ago
I found a different solution to the "getting around the screen" problem: set your keyboard repeat rate to 100 keys/s.
Upside: works anywhere, much lighter mental load, relatively easy to learn and adjust to.
Downside: some programs (ironically, mainly Emacs) can't keep up, and scrolling becomes choppy.
On Linux this is quite easy. When I was using Windows, there was no good solution for USB keyboards, so I hacked up a driver to do it: https://github.com/CyberShadow/KeyboardEmperor https://github.com/CyberShadow/KeyboardEmperor (signing keys not included).
- enriquto 5y ago> set your keyboard repeat rate to 100 keys/s. also, you can reduce the delay so that repetitions start sooner. With some practice and care you can reduce the delay to about 0.15 seconds and learn to fly over your keyboard xset r rate 150 255 # delay=150 (milliseconds) rate=255 (keys per second) at this point it's faster and easier to click left arrow than ^A, but of course it's not for everybody...
- mssdvd 5y agoIf you are on sway you can do the same: https://wiki.archlinux.org/title/Sway#Typematic_delay_and_rate https://wiki.archlinux.org/title/Sway#Typematic_delay_and_ra... To see the default value use xset -q
- layer8 5y agoIncidentally, high keyboard repeat rates is an important reason why I prefer spaces over tabs —- so that the horizontal cursor speed remains constant. (I’m serious.)
- r-zip 5y agoI found Emacs could keep up after the gccemacs update.