On 2013-09-02 19:56, H. S. Teoh wrote:
Well, personally I like to structure my code so that such big files
don't happen. :) But then again, there's *cough*std.algorithm*ahem*...
But I have to say that even with overly-large files, vim's concept of
using search to find stuff instead of scrolling and trying to find
things visually, helps one get into a mindset that makes navigating
large source files more manageable. I used to be a big fan of visual
navigation -- pgUp, pgDn, paragraph up, paragraph down, etc., but beyond
500 lines or so, they quickly become impractical. Having a 1-key search
function (that doesn't involve popups and other such annoyances) with
reversible direction is a far superior approach. It also saves a LOT of
keystrokes spent navigating horizontally when trying to reach a specific
point on a line: no need to hit left/right keys 40 times or move your
hand to the mouse and back, just search for a pair of characters (3-4
keystrokes) and you're exactly where you need to be. It took me a while
to get used to this mode of navigation, but I found it far superior to
whatever it was I used to do.
I really like the fuzzy search in TextMate. One hotkey for files and one
for classes/functions in the current file. If I don't type anything I
get the full list, which gives a nice overview of a file. Although it's
only names, no signatures.
--
/Jacob Carlborg
