Comment by troupo
1 year ago
> 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.
Or Cmd+Click/Ctrl+Click in an IDE
1 year ago
> 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.
Or Cmd+Click/Ctrl+Click in an IDE
Uhhh that would involve a mouse, gross ; )
Do you use a keyboard to browse the internet?
On unfamiliar codebases a mouse with back and forward buttons can be quite a fast and convenient way to get the "lie of the land".
I often do this inside GitHub's browser-based editor.
> Do you use a keyboard to browse the internet?
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.
1 reply →
"Uhhh that would involve a precision action with a tool specifically designed for precision actions" ;)
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)
2 replies →