M-x gdb : showing a selected buffer where it should be ?

M-x gdb : showing a selected buffer where it should be ?

[jonetsu]

In a M-x gdb session, with gdb-many-windows non nil (many windows
shown) putting the cursor in a window and selecting a buffer to show,
like the scratch buffer in the window where the cursor is at, as it
would normally be always the case, does nto work.  Instead 'something'
insists to _always_ show a selected buffer where the gdb interaction
window is, replacing the gbd interaction window.

sr-speedbar is also active.

Is there a way to bring sense to this and have emacs behave normally
regarding this, showing a selected buffer in the window where the
cursor currently is located while debugging ?

Re: M-x gdb : showing a selected buffer where it should be ?

[Eli Zaretskii]

> Date: Sat, 8 Jun 2019 18:13:07 -0400
> From: jonetsu <jonetsu@teksavvy.com>
> 
> In a M-x gdb session, with gdb-many-windows non nil (many windows
> shown) putting the cursor in a window and selecting a buffer to show,
> like the scratch buffer in the window where the cursor is at, as it
> would normally be always the case, does nto work.  Instead 'something'
> insists to _always_ show a selected buffer where the gdb interaction
> window is, replacing the gbd interaction window.
> 
> sr-speedbar is also active.

If you don't start sr-speedbar, does the problem go away?

> Is there a way to bring sense to this and have emacs behave normally
> regarding this, showing a selected buffer in the window where the
> cursor currently is located while debugging ?

Please describe the scenario in more detail.  I've read your
description more than once, and couldn't understand what exactly are
you doing after "M-x gdb" and "M-x gdb-many-windows" (or its
equivalent on the menu bar).  Specifically, after selecting a buffer
to be displayed in a window, what do you do to trigger that
"something" which insists on showing a selected buffer where the gdb
interaction buffer?

Perhaps start by trying to reproduce the problem in "emacs -Q".  If it
doesn't reproduce there, some of your customizations are responsible.