From 9fb0c6f5fc7a6215f266c1cc6d48716daa6f1ab0 Mon Sep 17 00:00:00 2001 From: Nick Roberts Date: Tue, 14 Feb 2006 21:42:11 +0000 Subject: [PATCH] (GDB Graphical Interface): Replace gdb-use-inferior-io-buffer with gdb-use-separate-io-buffer. --- man/building.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/man/building.texi b/man/building.texi index f621706fbbe..ea8055c1cab 100644 --- 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, -- 2.39.2