I used split pane when I was writing utilities on SunOS/early Solaris.
It allows you to say, keep the definitions at the top of some piece
of code visible, while you're writing code that references them
in the second pane. On occasion, I've even had three panes open.
More than that, was too much.
That should also tell you, that I'm not a programmer, and my
source files weren't partitioned or structured well. (It would
be quite likely, that my source file was too long.) I'm a
hardware guy, and the utilities I write do things like
test the hardware, or in other cases, manipulate CAD files.
(I've used a few different languages over the years.)
If I pour twenty pages of code into one file, I need to be
able to view the definition section, while I'm adding code
near the bottom.
That explains so why I like you so much. As I never wanted to be a
programmer at all. But I was an electronic engineer who fell into
designing computers in the 70's and 80's. Not consumer grade stuff, but
for the military and then later for the professional market.
But all of the famous people like Gary Kildall, Paul Allen, Steve Jobs,
Steve Woz, and heaven forbid even Bill Gates were doing was just child's
play compared to what I was doing. But all I got was a paycheck.
And back then before a programmer could fully understand your hardware,
it was far easier to tackle the software and to do it yourself. You know
for testing purposes at least. I got better and better at it of course.
And I didn't care how sloppy my programming was, just so I could
understand it was all that mattered.
I was really picky about bugs though. As I could see bugs appearing
while I was programming. So I could fix them right away. I only have one
regard that I knew of if somebody used one program right at the start
just seconds before midnight, one varaible would be off by one day. I
let that one slide as I thought nobody would do that anyway. And to my
knowledge nobody ever did. ;-) But I lost sleep over that one. :-(