Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
E-mail is so often reformatted, munged and quoted that depending on line numbers being the same on the sender's side seems foolish.
PS. I use Emacs for virtually everything so C-N, C-P and M-N, M-P get used for that kind of navigation.
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.)
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)
> 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`