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

[Stefan Monnier]

>     I suspect a major reason is that my window manager has no trouble
>     handling dozens of windows (aka frames), whereas yours makes it
>     more painful.

> I don't feel that.  My objection is to something iconifying and
> deiconifying while I'm in the middle of using it.

So making it invisible/visible instead of iconified/deiconified wouldn't
help, would it?
The current code should not do either of them "in the middle of using it"
any more.

> I don't mean to defend Windows, but I don't feel it has a problem wrt frames
> (except wrt mouse-follows-focus).

I use(d) focus-follows-mouse under XP quite happily.

> BTW, as long as you're in the debugger code (feature-creep warning): What
> about using function-called-at-point (or symbol-at-point) to provide the
> default function to debug in debug-on-entry (as in describe-function)? Most
> of the time you use the debugger you're in an emacs-lisp buffer, so picking
> up a lisp symbol would be helpful.

Patch welcome,


        Stefan