bug#7896: 23.2.91; Multi-window gdb uses other frames confusingly

[Lars Ingebrigtsen]

Reuben Thomas <rrt@sc3d.org> writes:

> While using multi-window gdb, I opened another frame, and looked at a
> related source file in it, though not the one that currently contained
> the execution point. I then switched back to the gdb frame, and advanced
> execution until it reached a point in the file in the buffer currently
> displayed in the other frame. gdb raised this frame, which happened to
> fill the whole screen (although the focus remained in the gdb frame).
>
> I submit that this is rather unhelpful behavior: in multi-window mode,
> gdb should always show the current execution point in the source window.
> I don’t expect the behavior to change just because I happen to have the
> relevant buffer open in another frame.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Some people have multi frame setups they display side-by-side, and in
those cases, popping up a new window with the same buffer would be
unhelpful.  So different people have different preferences here, but it
sounds like what gdb does by default is reasonable.  (I haven't actually
tested this to see whether the behaviour is still the same.)

In any case, to customise complex window preferences like this, Emacs
uses the display-buffer-alist (and related) variables.

So I don't think there's anything to be done here on the Emacs side, and
I'm therefore closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no