Re: Exploring a code base?

[Gregory Heytings]

> As for discovering that a problem includes more places and symbols than 
> one originally envisioned: one can maintain a flat list of 
> functions/modules/whatever to look into, and add to that as more stuff 
> is being found.  You can do it in Org or even in a simple text buffer. 
> If there's really a need to maintain some structure, one can use Org's 
> level headings to that end.

Yes, this is almost word for word what Yuri explained in his first mail, 
and Stefan in his reply.  Yuri says that doing this is "tedious", Stefan 
that it is "not satisfactory".  So the question is: could this not be 
automated with a kind of stack or list of searches, in which one could 
navigate, instead of using a separate flat or structured text file?