summaryrefslogtreecommitdiff
path: root/man/building.texi
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2002-01-22 11:30:52 +0000
committerEli Zaretskii <eliz@gnu.org>2002-01-22 11:30:52 +0000
commit3605e23f6d5c6e5e66ee05aae0e54d0306d1a61d (patch)
treed8dfa4141d5ceaa8a2df1e17bb7c701905f04a1a /man/building.texi
parentc3f340751f88c53d4079042f19a572936b700bfe (diff)
downloademacs-3605e23f6d5c6e5e66ee05aae0e54d0306d1a61d.tar.gz
(Debugger Operation): Add index entries for fringe usage.
Diffstat (limited to 'man/building.texi')
-rw-r--r--man/building.texi5
1 files changed, 3 insertions, 2 deletions
diff --git a/man/building.texi b/man/building.texi
index 797ac2daa81..3ec41de772f 100644
--- a/man/building.texi
+++ b/man/building.texi
@@ -345,13 +345,14 @@ allowed. GUD assumes that the first argument not starting with a
@node Debugger Operation
@subsection Debugger Operation
+@cindex fringes, and current execution line in GUD
When you run a debugger with GUD, the debugger uses an Emacs buffer
for its ordinary input and output. This is called the GUD buffer. The
debugger displays the source files of the program by visiting them in
Emacs buffers. An arrow (@samp{=>}) in one of these buffers indicates
the current execution line.@footnote{Under a window system the arrow is
-displayed in the marginal area of the Emacs window.} Moving point in
-this buffer does not move the arrow.
+displayed in the marginal area of the Emacs window, called @dfn{the
+fringe}.} Moving point in this buffer does not move the arrow.
You can start editing these source files at any time in the buffers
that display them. The arrow is not part of the file's