sometimes.
There is a bug in window updating when there is both a trace buffer
-and an evaluation list - the source buffer doesnt get displayed.
+and an evaluation list - the source buffer doesn't get displayed.
-@item
+@item
Killing and reinserting an instrumented definition or parts of
it leaves marks in the buffer which may confuse Edebug later.
There are no other known bugs, so if you find any, please let me know.
There is nothing worse than a buggy debugger!
-@item
+@item
I need to rethink locally binding @code{debug-on-error},
@code{debug-on-quit}, and keyboard macro state variables. Should we
allow the global values to be changed by the user?
Better integration with standard debug.
@item
-Use @code{inhibit-quit} while edebugging?
+Use @code{inhibit-quit} while edebugging?
@item
Crawl mode would @code{sit-for} 0 or 1 in the outside window configuration