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

[Stefan Monnier]

> It works fine for `c' not at the top level: in the middle of debugging it
> does not iconify or remove or flash the frame. Thanks.

Good.

> Did you provide some way for users to get a different behavior from `q' and
> `c' at top level, besides iconifying?

No, no time for it.

> I notice the new variable `debugger-step-after-exit' - I tried changing its
> value to `t', but I noticed no change in behavior. What is this supposed to


Maybe it's new, but it pre-dates my recent changes.  The variable I added is
debugger-will-be-back.  But both of those are defvar'd, not defcustom'd,
meaning they're not customization variables.  They're used internally and
are meaningless to the end-user.

> I replaced `(bury-buffer)' by `(quit-window)' in function `debug', and it
> works perfectly for me. Would you consider making that change? It might work
> for you too, since `quit-window' does bury-buffer and only deletes the frame
> if the window is dedicated.

My window *is* dedicated, so no, it wouldn't do what I want because it would
kill my frame.

> But I guess you want to iconify if the window is dedicated, right? Is
> there not some way to use `quit-window' so that both of us are satisfied?
> It is a fairly flexible function, with different options.  Could you at
> least take a look at it?

I don't see any relevant options.  The problem is that we're both in exactly
the same situation (a dedicated frame) whereas we want different behaviors.
It can't be decided automatically, and instead requires a config var.

> Otherwise, I will just have to redefine `debug' for my own use, replacing
> `(bury-buffer)' by `(quit-window)' - seems a shame. There must be a simple
> way to allow both possibilities: iconify and delete frame.

Plus a third: leave it displayed.


        Stefan