3 ms·

Interesting.. I've never used "Go to line" in that way, probably because my text editor never has line numbers showing. For me it is always to jump to the poin

Interesting.. I've never used "Go to line" in that way, probably because my text editor never has line numbers showing. For me it is always to jump to the point of an exception or somesuch.. maybe I'll try it for a while. PS. I use Emacs for virtually everything so C-N, C-P and M-N, M-P get used for that kind of navigation.

hboon 15y ago
I use MacVim. When you want to edit or add some code, isn't it more common to want to do it at a particular spot rather than reacting to a exception/warning? That's how I do it anyway. The only reasons I can come up with off the top of my head to do otherwise is if someone is doing heavy TDD or banging code into a Smalltalk debugger instead of a browser. How do you do it? (Genuine question. I almost always code by myself and have never been around anyone while they are productively working with an editor.)
- nicpottier 15y ago
  I've actually never met a developer that navigates a file using line numbers. Maybe it is the norm but I haven't seen it having worked with a few dozen developers over the years. Getting quick at line up/line down (C-N, C-P) and page up/page down (M-P, M-V in Emacs) seems to be a more common way of navigation. (C-S for quick search in Emacs being the other) I use "Go-to-line" almost exclusively to jump to the line where a stack trace is telling me there's an error. (TDD or not, stack traces are a way of life)
  - masklinn 15y ago
    > I've actually never met a developer that navigates a file using line numbers. Maybe it is the norm but I haven't seen it having worked with a few dozen developers over the years. > I use "Go-to-line" almost exclusively to jump to the line where a stack trace is telling me there's an error. yes that's pretty much it: use external tool to find some row (diff tells you this is where a chunk was changed, grep or ack tells you what you're looking for is there, ...), jump straight to row. Although usually I'll open the file directly at the right line in emacs (`e +line file`[0]), goto-line is only for the IDE. [0] where `e` is an alias for `emacsclient -n`

hboon 15y ago

I use MacVim. When you want to edit or add some code, isn't it more common to want to do it at a particular spot rather than reacting to a exception/warning? That's how I do it anyway. The only reasons I can come up with off the top of my head to do otherwise is if someone is doing heavy TDD or banging code into a Smalltalk debugger instead of a browser. How do you do it? (Genuine question. I almost always code by myself and have never been around anyone while they are productively working with an editor.)

nicpottier 15y ago
I've actually never met a developer that navigates a file using line numbers. Maybe it is the norm but I haven't seen it having worked with a few dozen developers over the years. Getting quick at line up/line down (C-N, C-P) and page up/page down (M-P, M-V in Emacs) seems to be a more common way of navigation. (C-S for quick search in Emacs being the other) I use "Go-to-line" almost exclusively to jump to the line where a stack trace is telling me there's an error. (TDD or not, stack traces are a way of life)
- masklinn 15y ago
  > I've actually never met a developer that navigates a file using line numbers. Maybe it is the norm but I haven't seen it having worked with a few dozen developers over the years. > I use "Go-to-line" almost exclusively to jump to the line where a stack trace is telling me there's an error. yes that's pretty much it: use external tool to find some row (diff tells you this is where a chunk was changed, grep or ack tells you what you're looking for is there, ...), jump straight to row. Although usually I'll open the file directly at the right line in emacs (`e +line file`[0]), goto-line is only for the IDE. [0] where `e` is an alias for `emacsclient -n`