←back to thread

Show HN: Hardtime.nvim – break bad habits and master Vim motions

(github.com)
214 points m4xshen | 1 comments | 18 May 25 12:08 UTC | HN request time: 0.211s | source
Show context
blahgeek ◴[18 May 25 15:40 UTC] 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(10): >>44022175 #>>44022261 #>>44022263 #>>44022311 #>>44022792 #>>44022889 #>>44023557 #>>44025366 #>>44032682 #>>44041520 #
rybosome ◴[18 May 25 16:03 UTC] 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. WhyNotHugo ◴[18 May 25 21:17 UTC] No.44024373[source]▶
Getting used to thinking about multi-line motions via 5j helped me train to visualise lines that way.

Over time, I started using things like 13dd or 7yy with more ease.

Of course, `set relativenumber` is always recommended.

> 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.

Yeah, you can't be a purist about it. If you're hard-focused and jjjjj is the first thing that comes to mind, then that's fine. When you're doing lighter work is when you have the spare mental capacity to train and improve on your workflow.