This made the biggest difference, more than anything else. It forced me to use hjkl and never the arrow keys.
Everything else is a bonus that comes by itself later.
51–60 of 89 posts
This made the biggest difference, more than anything else. It forced me to use hjkl and never the arrow keys.
Everything else is a bonus that comes by itself later.
Earlier quoted context omitted.
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 w…
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.
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
I was the exact same until I started using relative line numbers. Then I can just look at a line and see that it's N lines down and jump there immediately. With j or k repeat I'll often over shoot and then have to go back which is kind of annoying.
Earlier quoted context omitted.
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 w…
The best tip I got, was to rely more on search instead of other kind of movement. Especially when doing a bunch of editing. Things like easymotion/sneak/avy works best when reading/reviewing. While I loved multi cursor with sublime. After I moved to Vim, I’ve never needed it. It’s either search~repeat or a macro. Now I’m using emacs, and it’s mostly occur-mode and macro. Grep edit is nice for bigger refactoring.
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
I was the exact same until I started using relative line numbers. Then I can just look at a line and see that it's N lines down and jump there immediately. With j or k repeat I'll often over shoot and then have to go back which is kind of annoying.
When I started using Vim many years ago, I mapped the arrow keys to no-op. This made the biggest difference, more than anything else. It forced me to use hjkl and never the arrow keys. Everything else is a bonus that comes by itself later.
That's what hardtime solves.
I always find it funny when people say to not repeat h-l, w-W keys for horizontal movement. No way I am starting to count how many characters there are in front of my cursor just to have the satisfaction of typing "31-l"... I am totally going to spam some 2w 3w llll until I reach the desired position.
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
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 w…
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.
I always find it funny when people say to not repeat h-l, w-W keys for horizontal movement. No way I am starting to count how many characters there are in front of my cursor just to have the satisfaction of typing "31-l"... I am totally going to spam some 2w 3w llll until I reach the desired position.