2 ms·

I'm with you. The page gives "5k 12j" as an example, there's no way in the world it's faster for me to figure out that "12" is the right number faster than thro

• bumbledraven 2y ago
  > The page gives "5k 12j" as an example, there's no way in the world it's faster for me to figure out that "12" is the right number faster than through other means. If you add `set relativenumber` to your .vimrc, then the nth line up and the nth line down from from your current line will each have an n on the left-hand side. This lets you see at a glance which motion (e.g., `5k` or `12j`) will take you to a given line. https://jeffkreeftmeijer.com/vim-number/ https://jeffkreeftmeijer.com/vim-number/
• troyvit 2y ago
  I spend about half a second estimating. I think, eh that looks like about 30 lines so I'll go 30k. Then it's "oops I was off by 5 lines", so 5j (or jjjjj like you) and I'm there. Unfortunately if I land where I go on the first try it's bad because my fingers leave the home row for a fist pump. "Yesss!" The relative number bit actually drives me nuts. Mostly I'm fixing some code error "on line 465" of my code. I open up my spacevim and I'm always at line 0, so I have to gg then 465G and it's irritating. Probably need a better IDE.
  • inanutshellus 2y ago
    > I'm always at line 0 :set number :set relativenumber With both set, you see the actual line number you're on (e.g. line 465) and all other lines are relative. Personally I end up copy/pasting in/out of vim enough that I turn off line numbers but... FWIW, there's a way to not have the "always on 0" problem. :)