procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

(Debugger Operation): Add index entries for fringe usage.

Browse source
This commit is contained in:
Eli Zaretskii 2002-01-22 11:30:52 +00:00
parent c3f340751f
commit 3605e23f6d
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
man/building.texi
View file

@ -345,13 +345,14 @@ allowed. GUD assumes that the first argument not starting with a
@node Debugger Operation @node Debugger Operation
@subsection 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 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 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 debugger displays the source files of the program by visiting them in
Emacs buffers. An arrow (@samp{=>}) in one of these buffers indicates Emacs buffers. An arrow (@samp{=>}) in one of these buffers indicates
the current execution line.@footnote{Under a window system the arrow is the current execution line.@footnote{Under a window system the arrow is
displayed in the marginal area of the Emacs window.} Moving point in displayed in the marginal area of the Emacs window, called @dfn{the
this buffer does not move the arrow. fringe}.} Moving point in this buffer does not move the arrow.
You can start editing these source files at any time in the buffers 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 that display them. The arrow is not part of the file's