X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=doc%2Fmanual%2Fdebugger.texinfo;h=0d018f9c464d908d45f9560281baa553a1eafebc;hb=f4e8bca5eaa6e6db42299fe2f3852fb2e07508c7;hp=3e639d4570019b27e8b31464a4dd874ee4f08dea;hpb=8a8a8922802460741d6f8f6c11d71b1f414cf3a7;p=sbcl.git

diff --git a/doc/manual/debugger.texinfo b/doc/manual/debugger.texinfo
index 3e639d4..0d018f9 100644
--- a/doc/manual/debugger.texinfo
+++ b/doc/manual/debugger.texinfo
@@ -140,21 +140,7 @@ current frame.  For more information on debugger variable access, see
 In the debugger, it is possible to override the printing behaviour of
 the REPL.
 
-@defvr {Variable} sb-debug:*debug-print-variable-alist*
-
-An association list describing new bindings for special variables
-(typically *PRINT-FOO* variables) to be used within the debugger, e.g.
-@lisp
-((*PRINT-LENGTH* . 10) (*PRINT-LEVEL* . 6) (*PRINT-PRETTY* . NIL))
-@end lisp
-The variables in the @code{car} position are bound to the values in
-the @code{cdr} during the execution of some debug commands.  When
-evaluating arbitrary expressions in the debugger, the normal values of
-the printer control variables are in effect. @c FIXME: is this correct?
-@code{*debug-print-variable-alist*} does not contain any bindings
-initially.
-
-@end defvr
+@include var-sb-ext-star-debug-print-variable-alist-star.texinfo
 
 @node  Stack Frames
 @comment  node-name,  next,  previous,  up
@@ -790,7 +776,7 @@ form have been added or deleted.)
 If the heuristic doesn't work, the displayed source will be wrong, but will
 probably be near the actual source.  If the ``shape'' of the top-level form in
 the source file is too different from the original form, then an error will be
-signaled.  When the heuristic is used, the the source location commands are
+signaled.  When the heuristic is used, the source location commands are
 noticeably slowed.
 
 Source location printing can also be confused if (after the source was
@@ -830,7 +816,7 @@ some properties of the block start location:
 
 @item The block start location may be the same as the true location.
 
-@item The block start location will never be later in the the
+@item The block start location will never be later in the 
 program's flow of control than the true location.
 
 @item No conditional control structures (such as @code{if},
@@ -921,7 +907,7 @@ returning a value from the current stack frame.
 
 If @code{debug} is also at least 2, then  the code is @emph{partially
 steppable}. If @code{debug} is 3, the code is @emph{fully steppable}.
-@xref{Single Stepping} for details.
+@xref{Single Stepping}, for details.
 
 @end table
 
@@ -1007,8 +993,9 @@ proceed cases.
 @end deffn
 
 @deffn {Debugger Command} backtrace [@var{n}]
-Displays all the frames from the current to the bottom.  Only shows
-@var{n} frames if specified.  The printing is controlled by @code{*debug-print-variable-alist*}.
+Displays all the frames from the current to the bottom. Only shows
+@var{n} frames if specified. The printing is controlled by
+@code{*debug-print-variable-alist*}.
 @end deffn
 
 @deffn {Debugger Command} step
@@ -1023,7 +1010,7 @@ Selects the @code{continue} restart if one exists and starts single stepping.
 @c @cindex Breakpoints
 
 @c SBCL supports setting of breakpoints inside compiled functions and
-@c stepping of compiled code.  Breakpoints can only be set at at known
+@c stepping of compiled code.  Breakpoints can only be set at known
 @c locations (@pxref{Unknown Locations and Interrupts}), so these
 @c commands are largely useless unless the @code{debug} optimize quality
 @c is at least @code{2} (@pxref{Debugger Policy Control}).  These
@@ -1186,7 +1173,7 @@ function entry or exit.
 
 SBCL includes an instrumentation based single-stepper for compiled
 code, that can be invoked via the @code{step} macro, or from within
-the debugger. @xref{Debugger Policy Control} for details on enabling
+the debugger. @xref{Debugger Policy Control}, for details on enabling
 stepping for compiled code.
 
 Compiled code can be unsteppable, partially steppable, or fully steppable.