3 ms·
That's because scrolling with the mouse was a bit of an afterthough, I think. If you use motions, word objects and Ctrl+f/Ctrl+b you don't really notice this ch
by johncoltrane 16y ago
That's because scrolling with the mouse was a bit of an afterthough, I think. If you use motions, word objects and Ctrl+f/Ctrl+b you don't really notice this choppiness.
- adriand 16y agoActually I rarely use the mouse and was mainly referring to Ctrl-f/b and j/k, as well as w on long lines. I don't actively notice the choppiness until I use some other editer, but I wonder why it exists in the first place - is the rendering engine slow or something?
- losvedir 16y agoI suspect the reason is the same as on emacs: scrolling always occurs line by line (i.e., there is never a partial line visible at the top or bottom of the screen), whereas on most modern text editors it scrolls by pixel, so it's more of a continuous transition. I love emacs, but this is one of the sticking points that's really been bothering me of late. On a side note, it looks like with emacs's set-window-vscroll command, you can actually make it display a fraction of a line. Has anyone had any luck hacking this into a way to do smooth, continuous scrolling?