Re: Use of dedicated windows in gdb-mi.el

[Oleh Krehel]

Eli Zaretskii <address@hidden> writes:

>> From: Oleh Krehel <address@hidden>
>> Cc: address@hidden,  address@hidden,  address@hidden
>> Date: Mon, 09 Feb 2015 21:09:34 +0100
>> 
>> > I proposed to add a defcustom to prevent that.  I still think it would
>> > be a good solution, at least for popping window.
>> 
>> You're right, the dedicated window business was only a small part of the
>> problem.  The output window still pops up each time there's new output.
>> 
>> So even if I switch to *scratch* in the window of *output*, which I can
>> now do thanks to an advice, *output* will still pop up when something
>> new is printed by the program. So this defcustom would really be handy.
>
> AFAICS, it's a simple matter of adding a defcustom to be tested in
> gdb-display-io-buffer, causing the latter do nothing if the user says
> so.

Just instrumented `gdb-display-io-buffer', it's not the function that
makes the *output* buffer pop up when there's new output.