On Tue, 8 Apr 1997 21:05:36 -0400, Bill Dubuque <martigny.ai.mit.edu at wgd> said:
BD>  Dave Tenny <truesoft.com at dtenny> wrote to <Franz.com at Editi> on 8 Apr
BD> DT> 1997: : : ... Usually when I want to TRACE or BREAKPOINT a function, :
BD> DT> I'm already sitting with the point somewhere in the definition : of the
BD> DT> function I want to trace, as opposed to the call : site for that
BD> DT> function. ...
BD> 
BD> I agree this would be a useful capability (though it would require
BD> restructuring the prefix arg structure for all of the Tools commands in
BD> Editi 3.0).

Please take a look at the way the interaction between the editor and the
debugger is in AKCL with DBL installed. I believe that is the most
productive way of debugging a lisp program (short of using the Genera
environment).

(The following is assuming an emacs interface.) Basically, while editing a
file you bring your cursor to the line you want to break at and execute
some command to set a break point. When the computation hits that line you
break, and the file is pulled up in a second window with that line
highlighted. You can examine your stack in the listener window. When
stepping the current source lines keep being highlighted, pulling new
source files up when necessary. (Note that for this to work well, macros
are not expanded, so you step through the macros as well. You can mix files
that are loaded compiled and those that are loaded in the "debugable
form".) 

Th.