Outline view and old code

In a different thread,

On 2/23/2016 4:38 PM, Sam_L wrote:

There is a lot of ancient, hard-to-decipher code out there that has to
be maintained. This is where, in my experience anyway, RDi, and the
outline view, really help. If you have such code, IMHO you need RDi.

I live and breathe this exact scenario. Code written in the S/36 days,
full of left hand indicators, GOTO nests and everything is a hodgepodge
of dodgy variable names like NUM, NUM1 and TEST.

I am clearly doing something wrong, because I find the outline view
close to useless. Only rarely does it match up to the compiler cross
reference, and in the middle of editing, it comes and goes as the parser
chews away on the code-in-progress.

I'm not complaining in the least bit: I see this as a work in progress,
and I do see it getting better with each release. My point isn't to
complain, it's to try to find out how other people keep finding the
value in it that I can't seem to.

For context, I've been using RDi and ancestors since Code/400 ran on
OS/2. I'm a happy, happy RDi user who keeps a compiler listing open on
the other monitor.