summaryrefslogtreecommitdiff
path: root/lispref/debugging.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>1994-05-05 06:49:43 +0000
committerRichard M. Stallman <rms@gnu.org>1994-05-05 06:49:43 +0000
commit2e00781a52fd9b7723e9beb5205a7e52696288a0 (patch)
treedbdb6368a2c5790d6639e3068272831c37af8e26 /lispref/debugging.texi
parent742f715d96986d8c3e9198579d5de5f1a65cbe0a (diff)
entered into RCS
Diffstat (limited to 'lispref/debugging.texi')
-rw-r--r--lispref/debugging.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/lispref/debugging.texi b/lispref/debugging.texi
index 5b4905c30a..1b76597027 100644
--- a/lispref/debugging.texi
+++ b/lispref/debugging.texi
@@ -3,7 +3,7 @@
@c Copyright (C) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc.
@c See the file elisp.texi for copying conditions.
@setfilename ../info/debugging
-@node Debugging, Streams, Byte Compilation, Top
+@node Debugging, Read and Print, Byte Compilation, Top
@chapter Debugging Lisp Programs
There are three ways to investigate a problem in an Emacs Lisp program,