Subject: bug#9639: 24.0.90; Problem with bury-buffer in minibuffer-hide-completions

From: "Drew Adams" <[email-masked]>
Date: Tue, 4 Oct 2011 09:03:25 -0700

>  > But provide a user option, for users.
> 
> I now revived an option for this. It's called 
> `frame-auto-delete', is by default nil and, when non-nil,
> causes frames to be deleted in two cases:
> 
> - `quit-window' when its first argument is nil and the frame has been
>    specially created for the window's buffer.
> 
> - `bury-buffer' when its argument is nil and the selected window is
>    dedicated to its buffer.

Progress; thanks (haven't tried it, but sounds like progress).

But:
* You don't say what the non-deletion behavior is.
* The default behavior should be deletion.

`delete-frame' should be treated analogously to `delete-window'.