> the call stack will helpfully point out the file and line number of the location the error was thrown from, just a few keystrokes in vim will get you there.
Yes, using the vimium extension. My only problem is text inputs like this one, my muscle memory expects vim keys to work and I type a lot of jibberish that I have to clean up. I know there are extensions for that too but I can live with it.
I can definitely hit my Return key with more precision than I can drag a cursor over a 40x400px target but go off :P
(I use a Superior Technologies trackball because it's the only mouse I could find manufactured in the USA and it's really not very precise, it's kind of a self handicap to nudge me towards keyboard shortcuts, muscle memory gains just have a steeper curve on keyboard than mouse)
Maybe this is a physical development thing? Because i can't imagine a world in which my mouse is more accurate than my keyboard. The mouse requires two-way responsive action. I have to both move the mouse and observe the movement with my eyes to update the movement as necessary.
With the keyboard there is no such coordination, I simply think the thing i want to happen and press the appropriate keys.
Or Cmd+Click/Ctrl+Click in an IDE