summaryrefslogtreecommitdiff
path: root/doc/ref/scheme-using.texi
diff options
context:
space:
mode:
authorAndy Wingo <wingo@pobox.com>2010-10-07 13:06:57 +0200
committerAndy Wingo <wingo@pobox.com>2010-10-07 13:06:57 +0200
commit6e069bbfce57357ff279f19b09464b48de43fede (patch)
tree015df30e0d0f7092a2de5d6729f1aa9ddc5b5b35 /doc/ref/scheme-using.texi
parenta43b4d6e1f10e857f3d0cc0af69ba7c29a53b05e (diff)
downloadguile-6e069bbfce57357ff279f19b09464b48de43fede.tar.gz
update traps documentation (unfinished)
* doc/ref/Makefile.am: * doc/ref/guile.texi: * doc/ref/scheme-debugging.texi: Remove scheme-debugging.texi, which only described tracing. Tracing documentation is now in api-debugging. * doc/ref/scheme-using.texi (Evaluating Scheme Code): Remove reference to source traps, as that section is going away. * doc/ref/api-modules.texi (Included Guile Modules): Remove reference to Tracing. This section is a little silly, anyway... * doc/ref/api-evaluation.texi (VM Behaviour): Remove section, it is in api-debugging now. * doc/ref/api-debug.texi (Stacks, Frames): Rename sections from "Examining the Stack" and "Examining Stack Frames", respectively. (Traps): Update for current API. A big and not-quite-finished update.
Diffstat (limited to 'doc/ref/scheme-using.texi')
-rw-r--r--doc/ref/scheme-using.texi12
1 files changed, 5 insertions, 7 deletions
diff --git a/doc/ref/scheme-using.texi b/doc/ref/scheme-using.texi
index f6c2136e7..e9cff7621 100644
--- a/doc/ref/scheme-using.texi
+++ b/doc/ref/scheme-using.texi
@@ -1036,13 +1036,11 @@ region contains a balanced expression, or try to expand the region so
that it does; it uses the region exactly as it is.
@end table
-If you type @kbd{C-u} before one of these commands, GDS will
-immediately pop up a Scheme stack buffer, showing the requested
-evaluation, so that you can single step through it. (This is achieved
-by setting a @code{<source-trap>} trap at the start of the requested
-evaluation; see @ref{Source Traps} for more on how those work.) The
-Scheme stack display, and the options for continuing through the code,
-are described in the next two sections.
+If you type @kbd{C-u} before one of these commands, GDS will immediately
+pop up a Scheme stack buffer, showing the requested evaluation, so that
+you can single step through it. The Scheme stack display, and the
+options for continuing through the code, are described in the next two
+sections.
@node Displaying the Scheme Stack