←back to thread

154 points m4xshen | 2 comments | | HN request time: 0.485s | source
Show context
blahgeek ◴[] No.44022156[source]
I’ve been using vim for 10+ years. However I honestly don’t see the downside of repeating h or j to move up/down (with the key repeat delay adjusted to a small value). It’s more intuitive than using say 15j, which involves recognizing some number in the screen and then look at the keyboard to type because the upper number row cannot be easily touch typed
replies(8): >>44022175 #>>44022261 #>>44022263 #>>44022311 #>>44022792 #>>44022889 #>>44023557 #>>44025366 #
rybosome ◴[] No.44022311[source]
Agreed. I wonder if this is somewhat revealing of the mental processes of the creators.

To me, if my cursor is a few lines away from another line, the easiest way for me to get there is by either using h/j a few times, or looking at the absolute line number and doing that with gg.

Relative jumps are only useful to me in macros. Calculating a relative jump myself would 100% pull me out of the flow state where I just want to go up/down a few rows.

I have no proof of this, but I’d guess that the creator of this pattern didn’t feel the same way.

replies(3): >>44022443 #>>44023575 #>>44024373 #
1. eviks ◴[] No.44023575[source]
Why would you ever calculate relative jump yourself instead of having relative line numbers in the gutter?

And yes, for a few lines it's fine, the plugin has this number configurable.

replies(1): >>44024272 #
2. rybosome ◴[] No.44024272[source]
Thanks for letting me know, I wasn’t aware that was possible!