Comment by jazzyjackson
1 year ago
Good point re: using error messages. If I call a function incorrectly, 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.
> 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.
2 replies →
"Uhhh that would involve a precision action with a tool specifically designed for precision actions" ;)
3 replies →
Remarkable. With an ide you just press the hot key for next error and bam, it takes you to the exact line. (No you don’t need a mouse for this.)
In fact, with lsp you wouldn’t even write the error in the first place, saving you a big context switch to the terminal, running the compiler, reading the error, reading the file name, swapping back to edit, focus on the file again.