RE: debugger with pop-up-frames non-nil: keeps creating new frames

[Drew Adams]

    From: Stefan Monnier
    > emacs -q
    > If pop-up-frames is non-nil, each step (e.g. `d') in the debugger
    > creates a new frame. This is crazy.

    I think the only thing crazy about it is to set pop-up-frames to t while
    keeping display-buffer-reuse-frames to nil.  Such a setup will
    lead to the
    above problem in many more situations than just the debugger.

    Maybe display-buffer-reuse-frames should simply default to t,
    or at least
    default to t whenever pop-up-frames is non-nil.


I get the same bugged behavior (in Emacs -q) when these are both `t':

 pop-up-frames
 display-buffer-reuse-frames

In fact, it is in such a setup that I first discovered the bug.

Perhaps this problem has been fixed since the version I'm using? In my
version, a new frame is created with each debug step.

In GNU Emacs 22.0.50.2 (i386-mingw-nt5.1.2600)
 of 2005-04-16 on LAPTOP
Distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'

And, yes, I think the default value for `display-buffer-reuse-frames' should
be `t'. People upgrading from versions of Emacs that don't have this
variable will expect more or less unchanged behavior without having to
explicitly set this variable to `t'.

 - Drew