<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -50,18 +50,33 @@ get a list of commands and some help for each.
 
 3. WHAT'S NOT HERE YET IN DETAIL
 
-3.a) Showing frame arguments, subshell nesting in the call stack
+3.a) Showing frame arguments
 
-Like next, this can done with or without support from ksh, albeit
-faster with help from ksh. 
+This can done with or without support from ksh, albeit faster with
+help from ksh.
 
 3.b) Setting $0
 
 3.c) lots of other stuff including...
 
-  display expressions, signal handling
+  display expressions, signal handling, 
+  debugger commands:
+     debug
+     condition
+     file
+     handle
+     history
+     pwd
+     signal
+     tty
+     watch
 
   None of this is rocket science. Should be pretty straight-forward to
   add.
 
+4. WHAT MAY NEED MORE WORK AND SUPPORT FROM KSH
+
+4.a) stopping points that can be used for breakpoint
+
+
 </diff>
      <filename>README</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>91bb27d9b08986f854e687cfb2159eb2fc3313bf</id>
    </parent>
  </parents>
  <author>
    <name>R. Bernstein</name>
    <email>rocky@gnu.org</email>
  </author>
  <url>http://github.com/rocky/kshdb/commit/87e54e6c30a6c0ff8767ee82dd05679220563649</url>
  <id>87e54e6c30a6c0ff8767ee82dd05679220563649</id>
  <committed-date>2009-06-19T06:21:43-07:00</committed-date>
  <authored-date>2009-06-19T06:21:43-07:00</authored-date>
  <message>Revise as appropriate</message>
  <tree>4f1d503031c6da02e547665c1b04fc067814a43c</tree>
  <committer>
    <name>R. Bernstein</name>
    <email>rocky@gnu.org</email>
  </committer>
</commit>
