aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2005-06-17 13:42:18 +0000
committerRichard M. Stallman2005-06-17 13:42:18 +0000
commitd5ecfb935c4f9192ef0419331770838a8abd35f2 (patch)
tree61d022c4b7d4712e6114920b2f15801da3eed638
parent53099cfc9e2f52e1fac6dba35c207b442957ae46 (diff)
downloademacs-d5ecfb935c4f9192ef0419331770838a8abd35f2.tar.gz
emacs-d5ecfb935c4f9192ef0419331770838a8abd35f2.zip
(Debugger Commands): Minor fix.
-rw-r--r--lispref/debugging.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/lispref/debugging.texi b/lispref/debugging.texi
index 75be0462d66..0af1f16127d 100644
--- a/lispref/debugging.texi
+++ b/lispref/debugging.texi
@@ -350,7 +350,7 @@ structures of an interpreted function, but cannot do so in a
350byte-compiled function. If you would like to step through a 350byte-compiled function. If you would like to step through a
351byte-compiled function, replace it with an interpreted definition of 351byte-compiled function, replace it with an interpreted definition of
352the same function. (To do this, visit the source for the function and 352the same function. (To do this, visit the source for the function and
353type @kbd{C-M-x} on its definition.) You can not use the Lisp debugger 353type @kbd{C-M-x} on its definition.) You cannot use the Lisp debugger
354to step through a primitive function. 354to step through a primitive function.
355 355
356 Here is a list of Debugger mode commands: 356 Here is a list of Debugger mode commands: