* building.texi (GDB Graphical Interface): Remove misleading comparison

to an IDE (Bug#6128).

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 3030466f7fe154dcaa439a656f6e03e47007e67d..2b8482cf53bb5f5c765b89f63876caa2e2458575 100644 (file)
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,8 @@
+2010-05-07  Chong Yidong  <cyd@stupidchicken.com>
+
+       * building.texi (GDB Graphical Interface): Remove misleading comparison
+       to an IDE (Bug#6128).
+
 2010-05-03  Štěpán Němec  <stepnem@gmail.com>  (tiny change)
 
        * programs.texi (Man Page):

diff --git a/doc/emacs/building.texi b/doc/emacs/building.texi
index 6dbd5abf02635553ec21a6c9a31f9b11fc761f6a..41721a8afd0af93d61d042c1f0bd62e1b96254b1 100644 (file)
--- a/doc/emacs/building.texi
+++ b/doc/emacs/building.texi
@@ -836,12 +836,11 @@ Fully qualified class name derived from the expression surrounding point
 @subsection GDB Graphical Interface
 
   The command @code{gdb} starts GDB in a graphical interface, using
-Emacs windows for display program state information.  In effect, this
-makes Emacs into an IDE (interactive development environment).  With
-it, you do not need to use textual GDB commands; you can control the
-debugging session with the mouse.  For example, you can click in the
-fringe of a source buffer to set a breakpoint there, or on a stack
-frame in the stack buffer to select that frame.
+Emacs windows for display program state information.  With it, you do
+not need to use textual GDB commands; you can control the debugging
+session with the mouse.  For example, you can click in the fringe of a
+source buffer to set a breakpoint there, or on a stack frame in the
+stack buffer to select that frame.
 
   This mode requires telling GDB that its ``screen size'' is
 unlimited, so it sets the height and width accordingly.  For correct