(GDB Graphical Interface): Replace

gdb-use-inferior-io-buffer with gdb-use-separate-io-buffer.

diff --git a/man/building.texi b/man/building.texi
index f621706fbbe693cd58456ad1bb11d3824bc13575..ea8055c1cab08bb106f6975e822937b47c862d7d 100644 (file)
--- a/man/building.texi
+++ b/man/building.texi
@@ -841,7 +841,7 @@ displays the following frame layout:
 +--------------------------------+--------------------------------+
 @end example
 
-  However, if @code{gdb-use-inferior-io-buffer} is @code{nil}, the I/O
+  However, if @code{gdb-use-separate-io-buffer} is @code{nil}, the I/O
 buffer does not appear and the source buffer occupies the full width
 of the frame.
 
@@ -972,12 +972,12 @@ for variables defined in compound statements, the default value is
 
 @table @asis
 @item Input/Output Buffer
-@vindex gdb-use-inferior-io-buffer
-If the variable @code{gdb-use-inferior-io-buffer} is non-@code{nil},
+@vindex gdb-use-separate-io-buffer
+If the variable @code{gdb-use-separate-io-buffer} is non-@code{nil},
 the executable program that is being debugged takes its input and
 displays its output here.  Otherwise it uses the GUD buffer for that.
 To toggle whether GUD mode uses this buffer, do @kbd{M-x
-gdb-use-inferior-io-buffer}.  That takes effect when you next
+gdb-use-separate-io-buffer}.  That takes effect when you next
 restart the program you are debugging.
 
 The history and replay commands from Shell mode are available here,