Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!boulder!sunybcs!rutgers!iuvax!pur-ee!uiucdcs!uiucdcsb!liberte
From: liberte@uiucdcsb.cs.uiuc.edu
Newsgroups: comp.emacs
Subject: Re: using the internal Lisp debugger
Message-ID: <165400028@uiucdcsb>
Date: Wed, 18-Nov-87 00:20:00 EST
Article-I.D.: uiucdcsb.165400028
Posted: Wed Nov 18 00:20:00 1987
Date-Received: Sat, 21-Nov-87 11:22:43 EST
References: <29@goose.UUCP>
Lines: 23
Nf-ID: #R:goose.UUCP:29:uiucdcsb:165400028:000:940
Nf-From: uiucdcsb.cs.uiuc.edu!liberte    Nov 17 23:20:00 1987


The debugger is certainly better than nothing, but it could be better.
Some problems:

If you have more than two windows up, the debugger pops up in a different
window each single step.  It should use the same window.

If you start debugging with your on-line source in the wrong place and you
go and find the right place, and then you continue the debugger, it does
you the favor of returning the screen to the old set up.   What is needed
is two window configurations - one is the original, before debugging is
activated, and the other is whatever the user changes it to before
continuing the debugger.  Then there should be two ways to quit the
debugger, one for each window configuration.

Is anyone working on a source-level debugger that allows the user to
single step through source rather than tip-toe through the tulips, so
to speak?  That is one Gosling Emacs feature I miss.


Dan LaLiberte
liberte@a.cs.uiuc.edu
uiucdcs!liberte