3 ms·
That's fine for determining what line you're on, but visible line numbers make it much easier to jump to a particular line. I've only recently set number in my
by dionidium 14y ago
That's fine for determining what line you're on, but visible line numbers make it much easier to jump to a particular line. I've only recently set number in my .vimrc and wish I'd have done it sooner.
- ori_b 14y agoI do that by jumping to the particular line. :<linenum> or <linenum>G does that.
- hesitz 14y agoI think the point is that it's harder to see what line number you want to jump to if you don't have line numbering on. . . .
- Scriptor 14y agoRight, the alternative is to just sort of guess how much you need to ctrl-u/d or j and k to get to a specific line. Also, I guess it depends on screen size. I usually have plenty so the line numbers' usefulness outweighs the extra space required, at least for me.
- dionidium 14y agoYes, that's exactly my point
- dionidium 14y agoYes, that's how we all jump to a particular line :) It's just easier to target a specific line when numbering is turned on, as hesitz said.
- nathan_long 14y agoThey also make it much easier to find the line number named in an exception backtrace. :)
- ralph 14y agoDo you use (){}[] and others to move about? I rarely need to know the line number to move to on the screen.
- scott_w 14y agoThat only really works well if the line you want is visible. I've found searching to be much quicker, since I know class/method/variable names more than I know line numbers - we follow reasonably standard names for things in the projects we work on.